Release 4 Snapshot 3: Connectathon 32 Base

This page is part of the Snapshot #3 for 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 R5 , released to support Connectathon 32 . For a full list of available versions, see the Directory of published versions . Page versions: R4B R4 R3

Using Codes Code Systems Value Sets Concept Maps Identifier Systems 4.3.14.259 Code System http://terminology.hl7.org/CodeSystem/audit-entity-type

Example Observation/example (JSON)

Source Resource XML / JSON
Security Orders and Observations Work Group   Maturity Level : 3 N/A Trial Use Use Context Standards Status : Any This is a code system defined by the FHIR project. Summary Defining URL: http://terminology.hl7.org/CodeSystem/audit-entity-type Version: 4.0.1 Name: AuditEventEntityType Title: Audit event entity type Definition: Code for the entity type involved in the audit event. Committee: Informative Security Compartments : Device , Encounter , Patient , Practitioner , RelatedPerson Work Group OID: 2.16.840.1.113883.4.642.4.1134 (for OID based terminology systems)
This Code system is used in the following value sets: ValueSet: Audit event entity type (Code for the entity type involved in the audit event.)

This code system http://terminology.hl7.org/CodeSystem/audit-entity-type defines the following codes: Code Display Definition 1 Person Person 2 Raw JSON System Object System Object 3 ( canonical form Organization Organization 4 + also see JSON Format Specification Other Other   )

See the full registry of code systems defined as part of FHIR. Simple Weight Example

{
  "resourceType" : "Observation",
  "id" : "example",
  "text" : {
    "status" : "generated",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p><b>Generated Narrative: Observation</b><a name=\"example\"> </a></p><div style=\"display: inline-block; background-color: #d9e0e7; padding: 6px; margin: 4px; border: 1px solid #8da1b4; border-radius: 5px; line-height: 60%\"><p style=\"margin-bottom: 0px\">Resource Observation &quot;example&quot; </p></div><p><b>status</b>: <span title=\"   the mandatory quality flags:   \">final</span></p><p><b>category</b>: <span title=\"  category code is A code that classifies the general type of observation being made. This is used for searching, sorting and display purposes. \">Vital Signs <span style=\"background: LightGoldenRodYellow; margin: 4px; border: 1px solid khaki\"> (<a href=\"http://terminology.hl7.org/4.0.0/CodeSystem-observation-category.html\">Observation Category Codes</a>#vital-signs)</span></span></p><p><b>code</b>: <span title=\"  \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    \">Body Weight <span style=\"background: LightGoldenRodYellow; margin: 4px; border: 1px solid khaki\"> (<a href=\"https://loinc.org/\">LOINC</a>#29463-7; <a href=\"https://loinc.org/\">LOINC</a>#3141-9 &quot;Body weight Measured&quot;; <a href=\"https://browser.ihtsdotools.org/\">SNOMED CT</a>#27113001 &quot;Body weight&quot;; clinical-codes#body-weight)</span></span></p><p><b>subject</b>: <a href=\"patient-example.html\">Patient/example</a> &quot;Peter CHALMERS&quot;</p><p><b>encounter</b>: <a href=\"encounter-example.html\">Encounter/example</a></p><p><b>effective</b>: 2016-03-28</p><p><b>value</b>: <span title=\"   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    &quot;tablet&quot;), etc. For these, something else is required (e.g. SNOMED CT)\n     \">185 lbs<span style=\"background: LightGoldenRodYellow\"> (Details: UCUM code [lb_av] = 'lb_av')</span></span></p></div>"
  },
  "status" : "final",
  "category" : [{
    "coding" : [{
      "system" : "http://terminology.hl7.org/CodeSystem/observation-category",
      "code" : "vital-signs",
      "display" : "Vital Signs"
    }]
  }],
  "code" : {
    "coding" : [{
      "system" : "http://loinc.org",
      "code" : "29463-7",
      "display" : "Body Weight"
    },
    {
      "system" : "http://loinc.org",
      "code" : "3141-9",
      "display" : "Body weight Measured"
    },
    {
      "system" : "http://snomed.info/sct",
      "code" : "27113001",
      "display" : "Body weight"
    },
    {
      "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" : {
    "value" : 185,
    "unit" : "lbs",
    "system" : "http://unitsofmeasure.org",
    "code" : "[lb_av]"
  }
}

Explanation of the columns that may appear on this page: Level A few code lists that FHIR defines are hierarchical - each code is assigned a level. See Code System for further information. Source The source of the definition of the code (when the value set draws in codes defined elsewhere) Code The code (used as the code in the resource instance). If the code is in italics, this indicates Usage note: every effort has been made to ensure that the code is examples are correct and useful, but they are not selectable ('Abstract') Display The display (used in the display element of a Coding ). If there is no display, implementers should not simply display the code, but map the concept into their application Definition An explanation of the meaning normative part of the concept Comments Additional notes about how to use the code specification.