FerroEHR
importeddata/ferroehr
A pure-Rust openEHR Clinical Data Repository: ITS-REST 1.1.0, AQL 1.1, PostgreSQL 18-native storage.
Machine-generated from the listed sources and not yet reviewed by a human.
- Category
- Data & Standards
- Subcategory
- unknown
- License
- MIT(osi)
- Status
- active
- Maturity
- deployed
- Organization
- unknown
- Country
- unknown
- Homepage
- ferroehr.eu/
- Repository
- github.com/rubentalstra/FerroEHR
- Documentation
- unknown
- Tags
- cdr · clinical-data · ehr · erhbase · ferroehr · openehr · openehr-standard
- Regulatory
- unknown
Top contributors by commit count, from the project’s public repository. Avatars are served by their origin, not stored here. To be removed from this list, open an issue.
Computed from shared tags, weighted so a rare tag counts for more than a common one. These are suggestions, not curated relationships.
- cabolabs-ehrservercdr · clinical-data · ehr · openehr · openehr-standard
Open platform to manage and share standardized clinical data, designed by @ppazos at CaboLabs Health Informatics.
- ehrbasecdr · clinical-data · ehr · openehr
An open source openEHR server
- openehr-conformanceopenehr · openehr-standard
Documentation and examples related to the conformance on openEHR implementations.
- archetypesclinical-data · openehr
The validated and approved openEHR Arhcetypes used by DIPS AS
- clinical-embeddingsclinical-data · ehr
Repository for the Paper: „On the Importance of Step-wise Embeddings for Heterogeneous Clinical Time-Series“
- YAIBclinical-data · ehr
🧪Yet Another ICU Benchmark: a holistic framework for the standardization of clinical prediction model experiments. Provide custom datasets, cohorts, prediction tasks, endpoints, preprocessing, and…
- api.github.com/repos/rubentalstra/FerroEHRretrieved 2026-08-05 · via github-api
Machine-imported from GitHub search. Last push 2026-08-05, 4 stars, license reported as MIT. Category and schematic were assigned by keyword heuristics and are unreviewed.
Not yet verified by a human. Correct this record →
/v1/entries/22.json→ .entries["ferroehr"]
Entries are sharded 64 ways by a stable hash of the id, so a consumer can find any record without an index.