chronological-map-phenotypes
importeddata/chronological-map-phenotypes
Machine-readable version of electronic health record phenotypes for Kuan V. and Denaxas S. et al.
Machine-generated from the listed sources and not yet reviewed by a human.
- Category
- Data & Standards
- Subcategory
- unknown
- License
- MIT(osi)
- Status
- dormant
- Maturity
- deployed
- Organization
- unknown
- Country
- unknown
- Homepage
- unknown
- Documentation
- unknown
- Tags
- electronic-health-record · epidemiology · health-informatics · icd-10 · phenotype · read-code
- 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.
- ICD_GEMs.jlepidemiology · icd-10
ICD_GEMs.jl is a Julia package that allows to translate ICD-9 codes in ICD-10 and viceversa via the General Equivalence Mappings (GEMs) of the International Classification of Diseases (ICD).
- hermesicd-10
A library and microservice implementing the health and care terminology SNOMED CT with support for cross-maps, inference, fast full-text search, autocompletion, compositional grammar and the…
- Human Phenotype Ontology (HPO)phenotype
Standardised vocabulary of phenotypic abnormalities seen in human disease, widely used in rare-disease diagnostics.
- map-explorerphenotype
Use MAP to explore EHR data for individual patients.
- ehr-fhir-converterelectronic-health-record
Convert arbitrary EHR extracts to FHIR.
- magniFHIRelectronic-health-record
Basic Patient resource browser to provide visibility into your FHIR servers.
- api.github.com/repos/spiros/chronological-map-phenotypesretrieved 2026-08-05 · via github-api
Machine-imported from GitHub search. Last push 2024-06-28, 53 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/36.json→ .entries["chronological-map-phenotypes"]
Entries are sharded 64 ways by a stable hash of the id, so a consumer can find any record without an index.