FHIR IG analytics

Resources that use this resource

No resources found

Resources that this resource uses

Narrative

Note: links and images are rebased to the (stated) source

Source1

{
  "resourceType": "ConceptMap",
  "id": "R2-DiagnosticOrder-element-map-to-R4",
  "text": {
    "status": "generated",
    "div": "<!-- snip (see above) -->"
  },
  "extension": [
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
      "valueCode": "fhir"
    },
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
      "valueInteger": 0,
      "_valueInteger": {
        "extension": [
          {
            "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
            "valueCanonical": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r2.r4"
          }
        ]
      }
    },
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
      "valueCode": "trial-use",
      "_valueCode": {
        "extension": [
          {
            "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
            "valueCanonical": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r2.r4"
          }
        ]
      }
    }
  ],
  "url": "http://hl7.org/fhir/uv/xver/ConceptMap/R2-DiagnosticOrder-element-map-to-R4",
  "version": "0.1.0",
  "name": "R2DiagnosticOrderElementMapToR4",
  "title": "Cross-version mapping for FHIR DSTU2 DiagnosticOrder to FHIR R4 ServiceRequest",
  "status": "active",
  "experimental": false,
  "date": "2026-03-17T16:04:02.3876895-05:00",
  "contact": [
    {
      "name": "FHIR Infrastructure",
      "telecom": [
        {
          "system": "url",
          "value": "http://www.hl7.org/Special/committees/fiwg"
        }
      ]
    }
  ],
  "description": "This ConceptMap represents cross-version mappings for elements from a FHIR DSTU2 DiagnosticOrder to FHIR R4.",
  "jurisdiction": [
    {
      "coding": [
        {
          "system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code": "001",
          "display": "World"
        }
      ]
    }
  ],
  "sourceCanonical": "http://hl7.org/fhir/1.0",
  "targetUri": "http://hl7.org/fhir/4.0",
  "group": [
    {
      "source": "http://hl7.org/fhir/StructureDefinition/DiagnosticOrder",
      "sourceVersion": "1.0.2",
      "target": "http://hl7.org/fhir/StructureDefinition/ServiceRequest",
      "targetVersion": "4.0.1",
      "element": [
        {
          "code": "DiagnosticOrder.meta",
          "display": "meta",
          "target": [
            {
              "code": "ServiceRequest.meta",
              "display": "ServiceRequest.meta",
              "equivalence": "wider",
              "comment": "Element `DiagnosticOrder.meta` is mapped to FHIR R4 element `ServiceRequest.meta` as `SourceIsBroaderThanTarget`.\nThe mappings for `DiagnosticOrder.meta` do not cover the following types: Meta.\nThe mappings for `DiagnosticOrder.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId."
            }
          ]
        },
        {
          "code": "DiagnosticOrder.implicitRules",
          "display": "implicitRules",
          "target": [
            {
              "code": "ServiceRequest.implicitRules",
              "display": "ServiceRequest.implicitRules",
              "equivalence": "equivalent",
              "comment": "Element `DiagnosticOrder.implicitRules` is mapped to FHIR R4 element `ServiceRequest.implicitRules` as `Equivalent`.\nAsserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element as much as possible."
            }
          ]
        },
        {
          "code": "DiagnosticOrder.language",
          "display": "language",
          "target": [
            {
              "code": "ServiceRequest.language",
              "display": "ServiceRequest.language",
              "equivalence": "equivalent",
              "comment": "Element `DiagnosticOrder.language` is mapped to FHIR R4 element `ServiceRequest.language` as `Equivalent`.\nLanguage is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies  to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource  Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute)."
            }
          ]
        },
        {
          "code": "DiagnosticOrder.text",
          "display": "text",
          "target": [
            {
              "code": "ServiceRequest.text",
              "display": "ServiceRequest.text",
              "equivalence": "wider",
              "comment": "Element `DiagnosticOrder.text` is mapped to FHIR R4 element `ServiceRequest.text` as `SourceIsBroaderThanTarget`.\nThe mappings for `DiagnosticOrder.text` do not cover the following types: Narrative.\nThe mappings for `DiagnosticOrder.text` do not cover the following types based on type expansion: div, status.\nContained resources do not have narrative. Resources that are not contained SHOULD have a narrative."
            }
          ]
        },
        {
          "code": "DiagnosticOrder.contained",
          "display": "contained",
          "target": [
            {
              "code": "ServiceRequest.contained",
              "display": "ServiceRequest.contained",
              "equivalence": "equivalent",
              "comment": "Element `DiagnosticOrder.contained` is mapped to FHIR R4 element `ServiceRequest.contained` as `SourceIsBroaderThanTarget`.\nThis should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again."
            }
          ]
        },
        {
          "code": "DiagnosticOrder.subject",
          "display": "subject",
          "target": [
            {
              "code": "ServiceRequest.subject",
              "display": "ServiceRequest.subject",
              "equivalence": "wider",
              "comment": "Element `DiagnosticOrder.subject` is mapped to FHIR R4 element `ServiceRequest.subject` as `SourceIsBroaderThanTarget`.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `DiagnosticOrder.subject` with unmapped reference targets: Device, Group, Location, Patient."
            }
          ]
        },
        {
          "code": "DiagnosticOrder.orderer",
          "display": "orderer",
          "target": [
            {
              "code": "ServiceRequest.requester",
              "display": "ServiceRequest.requester",
              "equivalence": "relatedto",
              "comment": "Element `DiagnosticOrder.orderer` is mapped to FHIR R4 element `ServiceRequest.requester` as `RelatedTo`.\nThe mappings for `DiagnosticOrder.orderer` do not cover the following types based on type expansion: display, reference.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `DiagnosticOrder.orderer` with unmapped reference targets: Practitioner."
            }
          ]
        },
        {
          "code": "DiagnosticOrder.identifier",
          "display": "identifier",
          "target": [
            {
              "code": "ServiceRequest.identifier",
              "display": "ServiceRequest.identifier",
              "equivalence": "wider",
              "comment": "Element `DiagnosticOrder.identifier` is mapped to FHIR R4 element `ServiceRequest.identifier` as `SourceIsBroaderThanTarget`.\nThe mappings for `DiagnosticOrder.identifier` do not cover the following types: Identifier.\nThe mappings for `DiagnosticOrder.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value.\nThe identifier.type element is used to distinguish between the identifiers assigned by the orderer (known as the 'Placer' in HL7 v2) and the producer of the observations in response to the order (known as the 'Filler' in HL7 v2). For further discussion and examples see the [notes section](https://hl7.org/fhir/diagnos.html#4.22.4) below."
            }
          ]
        },
        {
          "code": "DiagnosticOrder.encounter",
          "display": "encounter",
          "target": [
            {
              "code": "ServiceRequest.encounter",
              "display": "ServiceRequest.encounter",
              "equivalence": "wider",
              "comment": "Element `DiagnosticOrder.encounter` is mapped to FHIR R4 element `ServiceRequest.encounter` as `SourceIsBroaderThanTarget`.\nThe mappings for `DiagnosticOrder.encounter` do not cover the following types based on type expansion: display, reference.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `DiagnosticOrder.encounter` with unmapped reference targets: Encounter."
            }
          ]
        },
        {
          "code": "DiagnosticOrder.reason",
          "display": "reason",
          "target": [
            {
              "code": "ServiceRequest.reasonCode",
              "display": "ServiceRequest.reasonCode",
              "equivalence": "equivalent",
              "comment": "Element `DiagnosticOrder.reason` is mapped to FHIR R4 element `ServiceRequest.reasonCode` as `Equivalent`.\nThis may be used to decide how the diagnostic investigation will be performed, or even if it will be performed at all.   Use CodeableConcept text element if the data is free (uncoded) text as shown in the [CT Scan example](https://hl7.org/fhir/diagnosticorder-example-di.html)."
            }
          ]
        },
        {
          "code": "DiagnosticOrder.supportingInformation",
          "display": "supportingInformation",
          "target": [
            {
              "code": "ServiceRequest.reasonReference",
              "display": "ServiceRequest.reasonReference",
              "equivalence": "relatedto",
              "comment": "Element `DiagnosticOrder.supportingInformation` is mapped to FHIR R4 element `ServiceRequest.reasonReference` as `SourceIsBroaderThanTarget`.\nElement `DiagnosticOrder.supportingInformation` is mapped to FHIR R4 element `ServiceRequest.supportingInfo` as `SourceIsBroaderThanTarget`.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `DiagnosticOrder.supportingInformation` with unmapped reference targets: Condition, DocumentReference, Observation.\nThis information includes diagnosis, clinical findings and other observations.  In laboratory ordering these are typically referred to as \"ask at order entry questions (AOEs)\". Examples include reporting the amount of inspired oxygen for blood gasses, the point in the menstrual cycle for cervical pap tests, and other conditions that influence test interpretations."
            },
            {
              "code": "ServiceRequest.supportingInfo",
              "display": "ServiceRequest.supportingInfo",
              "equivalence": "relatedto",
              "comment": "Element `DiagnosticOrder.supportingInformation` is mapped to FHIR R4 element `ServiceRequest.reasonReference` as `SourceIsBroaderThanTarget`.\nElement `DiagnosticOrder.supportingInformation` is mapped to FHIR R4 element `ServiceRequest.supportingInfo` as `SourceIsBroaderThanTarget`.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `DiagnosticOrder.supportingInformation` with unmapped reference targets: Condition, DocumentReference, Observation.\nThis information includes diagnosis, clinical findings and other observations.  In laboratory ordering these are typically referred to as \"ask at order entry questions (AOEs)\". Examples include reporting the amount of inspired oxygen for blood gasses, the point in the menstrual cycle for cervical pap tests, and other conditions that influence test interpretations."
            }
          ]
        },
        {
          "code": "DiagnosticOrder.specimen",
          "display": "specimen",
          "target": [
            {
              "code": "ServiceRequest.specimen",
              "display": "ServiceRequest.specimen",
              "equivalence": "wider",
              "comment": "Element `DiagnosticOrder.specimen` is mapped to FHIR R4 element `ServiceRequest.specimen` as `SourceIsBroaderThanTarget`.\nThe mappings for `DiagnosticOrder.specimen` do not cover the following types based on type expansion: display, reference.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `DiagnosticOrder.specimen` with unmapped reference targets: Specimen.\nMany investigation requests will create a need for specimens, but the request itself is not actually about the specimens. This is provided for when the diagnostic investigation is requested on already existing specimens."
            }
          ]
        },
        {
          "code": "DiagnosticOrder.status",
          "display": "status",
          "target": [
            {
              "code": "ServiceRequest.intent",
              "display": "ServiceRequest.intent",
              "equivalence": "relatedto",
              "comment": "Element `DiagnosticOrder.status` is mapped to FHIR R4 element `ServiceRequest.status` as `RelatedTo`.\nElement `DiagnosticOrder.status` is mapped to FHIR R4 element `ServiceRequest.intent` as `RelatedTo`.\nThe mappings for `DiagnosticOrder.status` do not allow expression of the necessary codes, per the bindings on the source and target.\nTypically the system placing the order sets the status to \"requested\". Thereafter, the order is maintained by the receiver that updates the status as the request is handled."
            },
            {
              "code": "ServiceRequest.status",
              "display": "ServiceRequest.status",
              "equivalence": "relatedto",
              "comment": "Element `DiagnosticOrder.status` is mapped to FHIR R4 element `ServiceRequest.status` as `RelatedTo`.\nElement `DiagnosticOrder.status` is mapped to FHIR R4 element `ServiceRequest.intent` as `RelatedTo`.\nThe mappings for `DiagnosticOrder.status` do not allow expression of the necessary codes, per the bindings on the source and target.\nTypically the system placing the order sets the status to \"requested\". Thereafter, the order is maintained by the receiver that updates the status as the request is handled."
            }
          ]
        },
        {
          "code": "DiagnosticOrder.priority",
          "display": "priority",
          "target": [
            {
              "code": "ServiceRequest.priority",
              "display": "ServiceRequest.priority",
              "equivalence": "equivalent",
              "comment": "Element `DiagnosticOrder.priority` is mapped to FHIR R4 element `ServiceRequest.priority` as `Equivalent`.\nThe Order resource also has a priority. Generally, these should be the same, but they can be different. For instance, where the clinician indicates the order is urgent, but the subsequent workflow process overrules the priority for some reason. The effective default value is \"normal\"."
            }
          ]
        },
        {
          "code": "DiagnosticOrder.item",
          "display": "item",
          "target": [
            {
              "code": "ServiceRequest",
              "display": "ServiceRequest",
              "equivalence": "relatedto",
              "comment": "Element `DiagnosticOrder.item` is mapped to FHIR R4 element `ServiceRequest` as `SourceIsNarrowerThanTarget`.\nThere would always be at least one item in normal usage, but this is optional so that a workflow can quote order details without having to list the items."
            }
          ]
        },
        {
          "code": "DiagnosticOrder.item.code",
          "display": "code",
          "target": [
            {
              "code": "ServiceRequest.code",
              "display": "ServiceRequest.code",
              "equivalence": "equivalent",
              "comment": "Element `DiagnosticOrder.item.code` is mapped to FHIR R4 element `ServiceRequest.code` as `Equivalent`.\nMany laboratory tests and radiology tests embed the specimen/organ system in the test name, for example,  serum or serum/plasma glucose, or a chest xray. The specimen may not be recorded separately from the test code."
            }
          ]
        },
        {
          "code": "DiagnosticOrder.item.specimen",
          "display": "specimen",
          "target": [
            {
              "code": "ServiceRequest.specimen",
              "display": "ServiceRequest.specimen",
              "equivalence": "wider",
              "comment": "Element `DiagnosticOrder.item.specimen` is mapped to FHIR R4 element `ServiceRequest.specimen` as `SourceIsBroaderThanTarget`.\nThe mappings for `DiagnosticOrder.item.specimen` do not cover the following types based on type expansion: display, reference.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR DSTU2 element `DiagnosticOrder.item.specimen` with unmapped reference targets: Specimen.\nA single specimen should not appear in both DiagnosticOrder.specimen and DiagnosticOrder.item.specimen."
            }
          ]
        },
        {
          "code": "DiagnosticOrder.item.bodySite",
          "display": "bodySite",
          "target": [
            {
              "code": "ServiceRequest.bodySite",
              "display": "ServiceRequest.bodySite",
              "equivalence": "narrower",
              "comment": "Element `DiagnosticOrder.item.bodySite` is mapped to FHIR R4 element `ServiceRequest.bodySite` as `SourceIsNarrowerThanTarget`.\nIf the use case requires BodySite to be handled as a separate resource instead of an inline coded element (e.g. to identify and track separately)  then use the standard extension [body-site-instance](https://hl7.org/fhir/extension-body-site-instance.html)."
            }
          ]
        },
        {
          "code": "DiagnosticOrder.note",
          "display": "note",
          "target": [
            {
              "code": "ServiceRequest.note",
              "display": "ServiceRequest.note",
              "equivalence": "wider",
              "comment": "Element `DiagnosticOrder.note` is mapped to FHIR R4 element `ServiceRequest.note` as `SourceIsBroaderThanTarget`.\nThe mappings for `DiagnosticOrder.note` do not cover the following types: Annotation.\nThe mappings for `DiagnosticOrder.note` do not cover the following types based on type expansion: author[x], text, time."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/DiagnosticOrder",
      "sourceVersion": "1.0.2",
      "target": "http://hl7.org/fhir/1.0/StructureDefinition/extension-DiagnosticOrder.meta",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "DiagnosticOrder.meta",
          "display": "meta",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `DiagnosticOrder.meta` is mapped to FHIR R4 element `ServiceRequest.meta` as `SourceIsBroaderThanTarget`.\nThe mappings for `DiagnosticOrder.meta` do not cover the following types: Meta.\nThe mappings for `DiagnosticOrder.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/DiagnosticOrder",
      "sourceVersion": "1.0.2",
      "target": "http://hl7.org/fhir/1.0/StructureDefinition/extension-DiagnosticOrder.text",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "DiagnosticOrder.text",
          "display": "text",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `DiagnosticOrder.text` is mapped to FHIR R4 element `ServiceRequest.text` as `SourceIsBroaderThanTarget`.\nThe mappings for `DiagnosticOrder.text` do not cover the following types: Narrative.\nThe mappings for `DiagnosticOrder.text` do not cover the following types based on type expansion: div, status.\nContained resources do not have narrative. Resources that are not contained SHOULD have a narrative."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/DiagnosticOrder",
      "sourceVersion": "1.0.2",
      "target": "http://hl7.org/fhir/1.0/StructureDefinition/extension-DiagnosticOrder.identifier",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "DiagnosticOrder.identifier",
          "display": "identifier",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `DiagnosticOrder.identifier` is mapped to FHIR R4 element `ServiceRequest.identifier` as `SourceIsBroaderThanTarget`.\nThe mappings for `DiagnosticOrder.identifier` do not cover the following types: Identifier.\nThe mappings for `DiagnosticOrder.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value.\nThe identifier.type element is used to distinguish between the identifiers assigned by the orderer (known as the 'Placer' in HL7 v2) and the producer of the observations in response to the order (known as the 'Filler' in HL7 v2). For further discussion and examples see the [notes section](https://hl7.org/fhir/diagnos.html#4.22.4) below."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/DiagnosticOrder",
      "sourceVersion": "1.0.2",
      "target": "http://hl7.org/fhir/1.0/StructureDefinition/extension-DiagnosticOrder.status",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "DiagnosticOrder.status",
          "display": "status",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `DiagnosticOrder.status` is mapped to FHIR R4 element `ServiceRequest.status` as `RelatedTo`.\nElement `DiagnosticOrder.status` is mapped to FHIR R4 element `ServiceRequest.intent` as `RelatedTo`.\nThe mappings for `DiagnosticOrder.status` do not allow expression of the necessary codes, per the bindings on the source and target.\nTypically the system placing the order sets the status to \"requested\". Thereafter, the order is maintained by the receiver that updates the status as the request is handled."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/DiagnosticOrder",
      "sourceVersion": "1.0.2",
      "target": "http://hl7.org/fhir/1.0/StructureDefinition/extension-DiagnosticOrder.event",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "DiagnosticOrder.event",
          "display": "event",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `DiagnosticOrder.event` has a context of ServiceRequest based on following the parent source element upwards and mapping to `ServiceRequest`.\nElement `DiagnosticOrder.event` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nThis is not the same as an audit trail. It is a view of the important things that happened in the past. Typically, there would only be one entry for any given status, and systems may not record all the status events."
            }
          ]
        },
        {
          "code": "DiagnosticOrder.event.status",
          "display": "status",
          "target": [
            {
              "code": "Extension.extension:status",
              "equivalence": "equivalent",
              "comment": "Element `DiagnosticOrder.event.status` is part of an existing definition because parent element `DiagnosticOrder.event` requires a cross-version extension.\nElement `DiagnosticOrder.event.status` has a context of ServiceRequest based on following the parent source element upwards and mapping to `ServiceRequest`.\nElement `DiagnosticOrder.event.status` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "DiagnosticOrder.event.description",
          "display": "description",
          "target": [
            {
              "code": "Extension.extension:description",
              "equivalence": "equivalent",
              "comment": "Element `DiagnosticOrder.event.description` is part of an existing definition because parent element `DiagnosticOrder.event` requires a cross-version extension.\nElement `DiagnosticOrder.event.description` has a context of ServiceRequest based on following the parent source element upwards and mapping to `ServiceRequest`.\nElement `DiagnosticOrder.event.description` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "DiagnosticOrder.event.dateTime",
          "display": "dateTime",
          "target": [
            {
              "code": "Extension.extension:dateTime",
              "equivalence": "equivalent",
              "comment": "Element `DiagnosticOrder.event.dateTime` is part of an existing definition because parent element `DiagnosticOrder.event` requires a cross-version extension.\nElement `DiagnosticOrder.event.dateTime` has a context of ServiceRequest based on following the parent source element upwards and mapping to `ServiceRequest`.\nElement `DiagnosticOrder.event.dateTime` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "DiagnosticOrder.event.actor",
          "display": "actor",
          "target": [
            {
              "code": "Extension.extension:actor",
              "equivalence": "equivalent",
              "comment": "Element `DiagnosticOrder.event.actor` is part of an existing definition because parent element `DiagnosticOrder.event` requires a cross-version extension.\nElement `DiagnosticOrder.event.actor` has a context of ServiceRequest based on following the parent source element upwards and mapping to `ServiceRequest`.\nElement `DiagnosticOrder.event.actor` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/DiagnosticOrder",
      "sourceVersion": "1.0.2",
      "target": "http://hl7.org/fhir/1.0/StructureDefinition/extension-DiagnosticOrder.item.status",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "DiagnosticOrder.item.status",
          "display": "status",
          "target": [
            {
              "code": "Extension",
              "equivalence": "equivalent",
              "comment": "Element `DiagnosticOrder.item.status` has a context of ServiceRequest based on following the parent source element upwards and mapping to `ServiceRequest`.\nElement `DiagnosticOrder.item.status` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nIf the request has multiple items that have their own life cycles, then the items will have their own status while the overall diagnostic order is (usually) \"in-progress\"."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/DiagnosticOrder",
      "sourceVersion": "1.0.2",
      "target": "http://hl7.org/fhir/1.0/StructureDefinition/extension-DiagnosticOrder.note",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "DiagnosticOrder.note",
          "display": "note",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `DiagnosticOrder.note` is mapped to FHIR R4 element `ServiceRequest.note` as `SourceIsBroaderThanTarget`.\nThe mappings for `DiagnosticOrder.note` do not cover the following types: Annotation.\nThe mappings for `DiagnosticOrder.note` do not cover the following types based on type expansion: author[x], text, time."
            }
          ]
        }
      ]
    }
  ]
}