OMOP Concept 42538118
Transplanted heart-lung present
StandardObservationSNOMED739025007Clinical Finding
Maps from
8
Descendants
1
Valid from
31 Jan 2018
Valid to
31 Dec 2099
OMOP concepts
Concept Lookup Tool
Search 11M+ concepts across SNOMED, RxNorm, ICD-10 & LOINC.
Source codes that map to this concept
8 source codes normalize to Transplanted heart-lung present via the OMOP "Maps to" relationship.
| Vocabulary | Code | Name | Type |
|---|---|---|---|
| CIM10 | Z94.3 | Heart and lungs transplant status | Non-standard |
| ICD10 | Z94.3 | Heart and lungs transplant status | Non-standard |
| ICD10CM | Z94.3 | Heart and lungs transplant status | Non-standard |
| ICD10CN | Z94.3 | Heart and lungs transplant status | Non-standard |
| ICD10CN | Z94.300 | Heart and lungs transplant status | Non-standard |
| ICD10GM | Z94.3 | Heart and lungs transplant status | Non-standard |
| KCD7 | Z94.3 | Heart and lungs transplant status | Non-standard |
| Nebraska Lexicon | 739025007 | Heart-lung transplant recipient | Non-standard |
Synonyms
Alternative names recorded for Transplanted heart-lung present across source vocabularies.
- bloque cardiopulmonar trasplantado presente
- bloque cardiopulmonar trasplantado presente (hallazgo)
- Heart-lung transplant recipient
- Transplanted heart-lung present (finding)
Where it sits in the hierarchy
Ordered by distance - 1 is a direct parent or child.
Broader concepts
(17)Roll up to these when you need a wider cohort.
- 1Transplanted heart present
- 1Transplanted lung present
- 2Cardiac finding
- 2Lung finding
- 2Postoperative state
- 2Transplant present
- 3Cardiovascular finding
- 3Finding of region of thorax
- 3Lower respiratory tract finding
- 3Mediastinal finding
- 3Postprocedural state finding
- 3Viscus structure finding
- 4Clinical finding
- 4Finding of upper trunk
- 4Procedure related finding
- 4Respiratory finding
- 5Finding of trunk structure
Narrower concepts
(1)Included automatically when you query with descendants.
Get this concept via the API
Resolve Transplanted heart-lung present - and every code that maps to it - over HTTPS, against the current vocabulary release. No downloads, no local database.
curl "https://api.omophub.com/v1/concepts/42538118?include_relationships=true" \
-H "Authorization: Bearer $OMOPHUB_API_KEY"Get your free API key3,000 calls/month free · no credit card