{
  "resourceType": "StructureDefinition",
  "id": "ccdd81fc-150d-47cc-be94-fc08f78a6ed4",
  "meta": {
    "versionId": "6",
    "lastUpdated": "2021-03-04T21:43:41.635+00:00"
  },
  "url": "http://rti.org/fhir/0217529/StructureDefinition/EHRtoRegistryLaboratoryResultObservationProfile",
  "version": "0.1",
  "name": "EHRtoRegistryLaboratoryResultObservationProfile",
  "status": "draft",
  "experimental": false,
  "date": "2021-03-04T21:40:32.4377476Z",
  "publisher": "RTI International, Inc",
  "description": "This profile sets the expectations for communicating laboratory test results from EHR systems to clinical registries.",
  "fhirVersion": "4.0.1",
  "mapping": [
    {
      "identity": "argonaut-dq-dstu2",
      "uri": "http://unknown.org/Argonaut-DQ-DSTU2",
      "name": "Argonaut-DQ-DSTU2"
    },
    {
      "identity": "workflow",
      "uri": "http://hl7.org/fhir/workflow",
      "name": "Workflow Pattern"
    },
    {
      "identity": "sct-concept",
      "uri": "http://snomed.info/conceptdomain",
      "name": "SNOMED CT Concept Domain Binding"
    },
    {
      "identity": "v2",
      "uri": "http://hl7.org/v2",
      "name": "HL7 v2 Mapping"
    },
    {
      "identity": "rim",
      "uri": "http://hl7.org/v3",
      "name": "RIM Mapping"
    },
    {
      "identity": "w5",
      "uri": "http://hl7.org/fhir/fivews",
      "name": "FiveWs Pattern Mapping"
    },
    {
      "identity": "sct-attr",
      "uri": "http://snomed.org/attributebinding",
      "name": "SNOMED CT Attribute Binding"
    }
  ],
  "kind": "resource",
  "abstract": false,
  "type": "Observation",
  "baseDefinition": "http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-lab",
  "derivation": "constraint",
  "differential": {
    "element": [
      {
        "id": "Observation",
        "path": "Observation",
        "definition": "This profile was originally created to meet the 2015 Edition Common Clinical Data Set 'Laboratory test(s) and Laboratory value(s)/result(s)' requirements. It has been (lightly) updated for our EHR to registry exchange use case."
      },
      {
        "id": "Observation.code",
        "path": "Observation.code",
        "comment": "The typical patterns for codes are: \r\n\r\n1. A LOINC code either as a  translation from a \"local\" code or as a primary code, or\r\n2. A local code by itself, but only if no suitable LOINC exists,  or\r\n3. Both the local code and the LOINC code as a translation\r\n\r\nSystems SHALL be capable of sending the local code if one exists. When using LOINC, use either the SHORTNAME or LONG_COMMON_NAME field for the display.",
        "requirements": "Knowing the kind of observation is essential to understanding the observation."
      },
      {
        "id": "Observation.interpretation",
        "path": "Observation.interpretation",
        "comment": "Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant.  Often reported as one or more simple compact codes, this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result."
      },
      {
        "id": "Observation.bodySite",
        "path": "Observation.bodySite",
        "comment": "Only used if not implicit in code found in Observation.code.  In many systems, this may be represented as a related observation instead of an inline component.   \n\nIf the use case requires BodySite to be handled as a separate resource (e.g. to identify and track separately) then use the standard extension[bodySite](extension-bodysite.html)."
      }
    ]
  }
}