This page is part of the FHIR Specification (v4.0.1: R4 - Mixed Normative and STU) in it's permanent home (it will always be available at this URL). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R4B R4 R3
Orders and Observations Work Group | Maturity Level: N/A | Standards Status: Informative | Compartments: Device, Encounter, Patient, Practitioner, RelatedPerson |
Raw JSON (canonical form + also see JSON Format Specification)
Example of another TPMT haplotype observation
{ "resourceType": "Observation", "id": "example-TPMT-haplotype-two", "text": { "status": "generated", "div": "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p><b>Generated Narrative with Details</b></p><p><b>id</b>: example-TPMT-haplotype-two</p><p><b>status</b>: unknown</p><p><b>code</b>: Haplotype Call <span>(Details : {SNOMED CT code '363779003' = 'Genotype determination', given as 'Genotype determination'})</span></p><p><b>subject</b>: <a>E***********</a></p><p><b>issued</b>: 03/04/2013 3:30:10 PM</p><p><b>value</b>: *4 <span>(Details : {http://pharmakb.org code 'PA166128353' = 'PA166128353', given as '*4'})</span></p><p><b>derivedFrom</b>: <a>MolecularSequence/example-TPMT-two</a></p></div>" }, "extension": [ { "url": "http://hl7.org/fhir/StructureDefinition/observation-geneticsGene", "valueCodeableConcept": { "coding": [ { "system": "http://www.genenames.org", "code": "12014", "display": "TPMT" } ] } } ], "status": "unknown", "code": { "coding": [ { "system": "http://snomed.info/sct", "code": "363779003", "display": "Genotype determination" } ], "text": "Haplotype Call" }, "subject": { "reference": "Patient/example", "display": "E***********" }, "issued": "2013-04-03T15:30:10+01:00", "valueCodeableConcept": { "coding": [ { "system": "http://pharmakb.org", "code": "PA166128353", "display": "*4" } ] }, "derivedFrom": [ { "reference": "MolecularSequence/example-TPMT-two" } ] }
Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.