STU 3 Candidate

This page is part of the FHIR Specification (v1.4.0: STU 3 Ballot 3). 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: R5 R4B R4 R3 R2

Observation-example.json

Raw JSON (canonical form)

Simple Weight Example

{
  "resourceType": "Observation",
  "id": "example",
  "text": {
    "fhir_comments": [
      "    the mandatory quality flags:    "
    ],
    "status": "generated",
    "div": "<div><p><b>Generated Narrative with Details</b></p><p><b>id</b>: example</p><p><b>status</b>: final</p><p><b>category</b>: Vital Signs <span>(Details : {http://hl7.org/fhir/observation-category code 'vital-signs' = 'Vital Signs', given as 'Vital Signs'})</span></p><p><b>code</b>: Body Weight <span>(Details : {LOINC code '29463-7' = 'Body weight', given as 'Body Weight'}; {LOINC code '3141-9' = 'Body weight Measured', given as 'Body weight Measured'}; {SNOMED CT code '27113001' = 'Body weight (observable entity)', given as 'Body weight'}; {http://acme.org/devices/clinical-codes code 'body-weight' = '??', given as 'Body Weight'})</span></p><p><b>subject</b>: <a>Patient/example</a></p><p><b>encounter</b>: <a>Encounter/example</a></p><p><b>effective</b>: 28/03/2016</p><p><b>value</b>: 185 lbs<span> (Details: http://unitsofmeasure.org code [lb_av] = 'lb_av')</span></p></div>"
  },
  "status": "final",
  "category": {
    "fhir_comments": [
      "   category code is A code that classifies the general type of observation being made. This is used for searching, sorting and display purposes.  "
    ],
    "coding": [
      {
        "system": "http://hl7.org/fhir/observation-category",
        "code": "vital-signs",
        "display": "Vital Signs"
      }
    ]
  },
  "code": {
    "fhir_comments": [
      "   \n    Observations are often coded in multiple code systems.\n      - LOINC provides codes of varying granularity (though not usefully more specific in this particular case) and more generic LOINCs  can be mapped to more specific codes as shown here\n      - snomed provides a clinically relevant code that is usually less granular than LOINC\n      - the source system provides its own code, which may be less or more granular than LOINC\n     "
    ],
    "coding": [
      {
        "fhir_comments": [
          "    LOINC - always recommended to have a LOINC code    "
        ],
        "system": "http://loinc.org",
        "code": "29463-7",
        "display": "Body Weight",
        "_display": {
          "fhir_comments": [
            "  more generic methodless LOINC  "
          ]
        }
      },
      {
        "system": "http://loinc.org",
        "code": "3141-9",
        "display": "Body weight Measured",
        "_display": {
          "fhir_comments": [
            "  translation is more specific method = measured LOINC  "
          ]
        }
      },
      {
        "fhir_comments": [
          "    SNOMED CT Codes - becoming more common    "
        ],
        "system": "http://snomed.info/sct",
        "code": "27113001",
        "display": "Body weight"
      },
      {
        "fhir_comments": [
          "    Also, a local code specific to the source system    "
        ],
        "system": "http://acme.org/devices/clinical-codes",
        "code": "body-weight",
        "display": "Body Weight"
      }
    ]
  },
  "subject": {
    "reference": "Patient/example"
  },
  "encounter": {
    "reference": "Encounter/example"
  },
  "effectiveDateTime": "2016-03-28",
  "valueQuantity": {
    "fhir_comments": [
      "    In FHIR, units may be represented twice. Once in the\n    agreed human representation, and once in a coded form.\n    Both is best, since it's not always possible to infer\n    one from the other in code.\n\n    When a computable unit is provided, UCUM (http://unitsofmeasure.org)\n    is always preferred, but it doesn't provide notional units (such as\n    \"tablet\"), etc. For these, something else is required (e.g. SNOMED CT)\n      "
    ],
    "value": 185,
    "unit": "lbs",
    "system": "http://unitsofmeasure.org",
    "code": "[lb_av]"
  }
}

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.