SIMPLIFIER.NET - FHIRPath Playground

FHIRPath

If you Log in or sign up, you can edit this script yourself.

<StructureDefinition xmlns="http://hl7.org/fhir">
  <id value="ccdd81fc-150d-47cc-be94-fc08f78a6ed4" />
  <meta>
    <versionId value="6" />
    <lastUpdated value="2021-03-04T21:43:41.635+00:00" />
  </meta>
  <url value="http://rti.org/fhir/0217529/StructureDefinition/EHRtoRegistryLaboratoryResultObservationProfile" />
  <version value="0.1" />
  <name value="EHRtoRegistryLaboratoryResultObservationProfile" />
  <status value="draft" />
  <experimental value="false" />
  <date value="2021-03-04T21:40:32.4377476Z" />
  <publisher value="RTI International, Inc" />
  <description value="This profile sets the expectations for communicating laboratory test results from EHR systems to clinical registries." />
  <fhirVersion value="4.0.1" />
  <mapping>
    <identity value="argonaut-dq-dstu2" />
    <uri value="http://unknown.org/Argonaut-DQ-DSTU2" />
    <name value="Argonaut-DQ-DSTU2" />
  </mapping>
  <mapping>
    <identity value="workflow" />
    <uri value="http://hl7.org/fhir/workflow" />
    <name value="Workflow Pattern" />
  </mapping>
  <mapping>
    <identity value="sct-concept" />
    <uri value="http://snomed.info/conceptdomain" />
    <name value="SNOMED CT Concept Domain Binding" />
  </mapping>
  <mapping>
    <identity value="v2" />
    <uri value="http://hl7.org/v2" />
    <name value="HL7 v2 Mapping" />
  </mapping>
  <mapping>
    <identity value="rim" />
    <uri value="http://hl7.org/v3" />
    <name value="RIM Mapping" />
  </mapping>
  <mapping>
    <identity value="w5" />
    <uri value="http://hl7.org/fhir/fivews" />
    <name value="FiveWs Pattern Mapping" />
  </mapping>
  <mapping>
    <identity value="sct-attr" />
    <uri value="http://snomed.org/attributebinding" />
    <name value="SNOMED CT Attribute Binding" />
  </mapping>
  <kind value="resource" />
  <abstract value="false" />
  <type value="Observation" />
  <baseDefinition value="http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-lab" />
  <derivation value="constraint" />
  <differential>
    <element id="Observation">
      <path value="Observation" />
      <definition value="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." />
    </element>
    <element id="Observation.code">
      <path value="Observation.code" />
      <comment value="The typical patterns for codes are: &#xD;&#xA;&#xD;&#xA;1. A LOINC code either as a  translation from a &quot;local&quot; code or as a primary code, or&#xD;&#xA;2. A local code by itself, but only if no suitable LOINC exists,  or&#xD;&#xA;3. Both the local code and the LOINC code as a translation&#xD;&#xA;&#xD;&#xA;Systems 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 value="Knowing the kind of observation is essential to understanding the observation." />
    </element>
    <element id="Observation.interpretation">
      <path value="Observation.interpretation" />
      <comment value="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." />
    </element>
    <element id="Observation.bodySite">
      <path value="Observation.bodySite" />
      <comment value="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.   &#xA;&#xA;If 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)." />
    </element>
  </differential>
</StructureDefinition>

name : EHRtoRegistryLaboratoryResultObservationProfile

{

}

<name value="EHRtoRegistryLaboratoryResultObservationProfile" />