SIMPLIFIER.NET - FHIRPath Playground

FHIRPath

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

<StructureDefinition xmlns="http://hl7.org/fhir">
  <meta>
    <lastUpdated value="2017-08-07T06:29:24.533-04:00" />
    <profile value="http://pchalliance.org/phdfhir/StructureDefintion/phdParentDeviceComponent" />
  </meta>
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="dev" />
  </extension>
  <url value="http://pchalliance.org/phdfhir/StructureDefinition/phdParentDeviceComponent" />
  <name value="phdParentDeviceComponent" />
  <status value="draft" />
  <date value="2017-07-07T11:39:51.3383228-04:00" />
  <description value="Base StructureDefinition for the parent DeviceComponent Resource for a PHD" />
  <purpose value="This resource describes the primary features of a Personal Health Device (PHD). It is referred to as the 'parent' resource since it contains the properties, production specification, and overall type of the PHD. In most cases, a PHD will only have a parent. A child DeviceComponent happens when the PHD happens to support more than one specialization. The child component will only contain information about the specialization." />
  <fhirVersion value="3.0.0" />
  <kind value="resource" />
  <abstract value="false" />
  <type value="DeviceComponent" />
  <baseDefinition value="http://hl7.org/fhir/StructureDefinition/DeviceComponent" />
  <derivation value="constraint" />
  <differential>
    <element id="DeviceComponent">
      <path value="DeviceComponent" />
      <definition value="The characteristics, operational status and capabilities of a medical-related component of a medical device. A PHD is JUST the medical-related component." />
      <comment value="For the initial scope, this DeviceComponent resource is only applicable to describe a single node in the containment tree that is produced by the context scanner in any medical device that implements or derives from the ISO/IEEE 11073 standard and that does not represent a metric. Examples for such a node are MDS, VMD, or Channel.&#xD;&#xA;&#xD;&#xA;With PHD medical units, there is no medical scanner and the unit is only a single node, a single 'simple' MDS, and it is static. Thus a PHD has no parent 'Device'.  When a PHD supports multiple device specializations, the single unit description is still the case. A specialization is just an way to organize a set of metric objects that tend to be generated by a single sensor, but the device could expose metric objects from several specializations which usually means it has more than one sensor. In PHDs that is rare. Since FHIR does not have a means to list multiple types for the DeviceComponent resource, child DeviceComponents are used to expose these additional specializations should they occur.&#xD;&#xA;&#xD;&#xA;Child DeviceComponents can appear in two ways, a single specialization that supports one or more sub-profiles, or a hydra PHD that supports multiple specializations." />
    </element>
    <element id="DeviceComponent.meta.profile">
      <path value="DeviceComponent.meta.profile" />
      <min value="1" />
    </element>
    <element id="DeviceComponent.identifier">
      <path value="DeviceComponent.identifier" />
      <slicing>
        <discriminator>
          <type value="value" />
          <path value="system" />
        </discriminator>
        <ordered value="true" />
        <rules value="open" />
      </slicing>
      <short value="Information that uniquely describes the device" />
      <definition value="The locally assigned unique identification of the device that is semantically meaningful outside of the FHIR resource context. An example would be the IEEE EUI-64 System-Id or transport address. For PHDs the systemIdentifier is required and the transportAddressIdentifier is highly recommended as this is what most end users see and can obtain from the device itself or device packaging." />
      <comment value="In future versions of FHIR the cardinality of this element will become [0..*] and this element will be used to report the system id and optionally the transport address." />
      <max value="*" />
    </element>
    <element id="DeviceComponent.identifier:systemIdIdentifier">
      <path value="DeviceComponent.identifier" />
      <sliceName value="systemIdIdentifier" />
      <short value="IEEE EUI-64 identifier" />
      <definition value="This entry contains the IEEE EUI-64. If absent (bad device) set to all zeros." />
      <min value="1" />
    </element>
    <element id="DeviceComponent.identifier.system">
      <path value="DeviceComponent.identifier.system" />
      <short value="IEEE EUI-64 identifier" />
      <definition value="Identifies the system as an IEEE EUI." />
      <min value="1" />
      <fixedUri value="urn:oid:1.2.840.10004.1.1.1.0.0.1.0.0.1.2680" />
    </element>
    <element id="DeviceComponent.identifier.value">
      <path value="DeviceComponent.identifier.value" />
      <definition value="The System id from the System-Id attribute as an 8-byte HEX string where each byte is separated by dashes, for example FE-ED-AB-EE-DE-AD-77-C3. " />
      <comment value="The formatting is specified in the IEEE document Guidelines for 64-bit Global Identifier.&#xD;&#xA;&#xD;&#xA;To allow the mapping of naughty, non-compliant proprietary devices that do not provide a system id, the value is set to all zeros in the same format, 00-00-00-00-00-00-00-00" />
      <min value="1" />
    </element>
    <element id="DeviceComponent.identifier:transportAddressIdentifier">
      <path value="DeviceComponent.identifier" />
      <sliceName value="transportAddressIdentifier" />
      <short value="Transport address identifier" />
      <definition value="This entry contains the transport address, for example the Bluetooth, ZigBee, USB, or mac address." />
      <comment value="USB does not have an 'address' as it is a point to point wired protocol. However, it does have a Vendor identification and Production identification number which together uniquely define the unit. For USB transports, the VID.PID in HEX is used as the transport identifier." />
    </element>
    <element id="DeviceComponent.identifier.system">
      <path value="DeviceComponent.identifier.system" />
      <min value="1" />
    </element>
    <element id="DeviceComponent.identifier.value">
      <path value="DeviceComponent.identifier.value" />
      <definition value="The transport address. If Bluetooth, use an EUI-48 such as 00-E5-DE-AD-77-C3. If a USB device use the VID.PID as HEX such as 0043.F90D. If a ZigBee address use an EUI-64 as with the system id. If a TCP/IP address use the standard IP address format such as 192.168.127.4" />
      <comment value="Transport addresses are supposed to be unique for a given device." />
      <min value="1" />
    </element>
    <element id="DeviceComponent.identifier:alternativeIdentifier">
      <path value="DeviceComponent.identifier" />
      <sliceName value="alternativeIdentifier" />
      <short value="Alternative identifiers" />
      <definition value="Alternative identifiers serving the business use case." />
      <max value="*" />
    </element>
    <element id="DeviceComponent.identifier.system">
      <path value="DeviceComponent.identifier.system" />
      <min value="1" />
    </element>
    <element id="DeviceComponent.type">
      <path value="DeviceComponent.type" />
      <definition value="The type or 'specialization' of the PHD. " />
      <comment value="In most cases a PHD supports only a single specialization such as a Blood Pressure monitor and only one DeviceComponent is needed and that specialization is recorded in this element. Since there is no way to indicate additional supported specialziations with this element (it has cardinality 1..1), additional child DeviceComponents are needed when multiple specializations and/or sub-profiles are present.&#xD;&#xA;&#xD;&#xA;The value entered in this element comes from the System-Type-Spec-List attribute which is unique to the 11073 20601 specification; 11073-10201 does not have such an attribute. If there is more than one specialization, the special HYDRA specialization value is entered here and child DeviceComponent resources are used to map the specializations. If there is only a single specialization but one or more sub profiles., the specialization is entered here and the sub profiles are handled in child DeviceComponents.&#xD;&#xA;&#xD;&#xA;Note that sub-profiles are a packaging of objects within a specialization that serve a special use case. For example, the Cardiovascular specialization has numerous objects that can represent all kinds of physical activities from treadmills to skiing. One sub-profile is a minimum set of objects needed to describe a step counter." />
    </element>
    <element id="DeviceComponent.type.coding">
      <path value="DeviceComponent.type.coding" />
      <slicing>
        <discriminator>
          <type value="value" />
          <path value="system" />
        </discriminator>
        <ordered value="true" />
        <rules value="open" />
      </slicing>
      <min value="1" />
    </element>
    <element id="DeviceComponent.type.coding:11073Type">
      <path value="DeviceComponent.type.coding" />
      <sliceName value="11073Type" />
      <definition value="The 11073 10101 code for the PHD specialization." />
      <comment value="This coding is provided by the System-Type-Spec-List attribute. Note that PoCDs do not have a System-Type-Spec-List but express specializations in different VMD objects." />
      <min value="1" />
      <max value="1" />
    </element>
    <element id="DeviceComponent.type.coding.system">
      <path value="DeviceComponent.type.coding.system" />
      <short value="Identifies IEEE 11073 10101 " />
      <definition value="This value identifies the IEEE 11073 10101 coding system" />
      <min value="1" />
      <fixedUri value="urn:iso:std:iso:11073:10101" />
    </element>
    <element id="DeviceComponent.type.coding.code">
      <path value="DeviceComponent.type.coding.code" />
      <short value="Device specialization code" />
      <definition value="The device specialization is obtained from the System-Type-Spec-List attribute if the attribute has only a single entry or only a single specialization with one or more sub profiles from that specialization. If it has multiple specializations, this value is fixed to 'hydra' and there will be child DeviceComponent resources handling the specializations. The attribute provides only the term code, the partition is always 'infra' which has value 8. Thus the code will be 8*2**16 + term code.&#xD;&#xA;&#xD;&#xA;When 'hydra' is used, the code is 528384 and the reference id is MDC_DEV_SPEC_PROFILE_HYDRA" />
      <min value="1" />
    </element>
    <element id="DeviceComponent.type.coding.display">
      <extension url="http://hl7.org/fhir/StructureDefinition/elementdefinition-translatable">
        <valueBoolean value="true" />
      </extension>
      <path value="DeviceComponent.type.coding.display" />
      <definition value="A human readable display descrbing the meaning of the code." />
      <comment value="This element should contain the reference identfier for the reported specialization code." />
    </element>
    <element id="DeviceComponent.type.coding:alternativeType">
      <path value="DeviceComponent.type.coding" />
      <sliceName value="alternativeType" />
      <comment value="The specialization expressed in the 11073Type 'slice' in an alternative coding system. If applications populate this entry the system and code elements shall be populated." />
    </element>
    <element id="DeviceComponent.type.coding.system">
      <path value="DeviceComponent.type.coding.system" />
      <min value="1" />
    </element>
    <element id="DeviceComponent.type.coding.code">
      <path value="DeviceComponent.type.coding.code" />
      <min value="1" />
    </element>
    <element id="DeviceComponent.lastSystemChange">
      <path value="DeviceComponent.lastSystemChange" />
      <definition value="The timestamp for the most recent system change which includes device configuration or setting change. This field is not provided by PHD devices via standardized exchange protocols and is, therefore, not required in this profile." />
      <comment value="A PHD is static and does not change and the appropriate value for this entry would be its manufacture date. However, this information is not available by protocol and shall not be used. Its absence indicates a static unit." />
      <max value="0" />
    </element>
    <element id="DeviceComponent.source">
      <path value="DeviceComponent.source" />
      <comment value="PHDs are considered medical devices only and are not part of a device complex which PoCD devices might be. The DeviceComponent is considered to represent the medical device subset of a device complex and since that is all a PHD is, this element is not used." />
      <max value="0" />
    </element>
    <element id="DeviceComponent.parent">
      <path value="DeviceComponent.parent" />
      <definition value="The link to the DeviceComponent resource representing the Personal Health Gateway (PHG) that processed the sensor data and converted it to FHIR" />
      <comment value="This element shall be present if a PHG is involved in generating the FHIR data." />
      <requirements value="The PHG does limited correction of the received data; in particular, any errors in the time line and mapping the time line to local time plus UTC offset" />
    </element>
    <element id="DeviceComponent.parent.reference">
      <path value="DeviceComponent.parent.reference" />
      <definition value="A reference to a location at which the PHG resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources." />
      <min value="1" />
    </element>
    <element id="DeviceComponent.operationalStatus">
      <path value="DeviceComponent.operationalStatus" />
      <comment value="OperationalStatus for the MDS, VMD, or Channel will be bound to a specific ValueSet that is defined in its profile. If used, a PHD is considered to be always on" />
    </element>
    <element id="DeviceComponent.parameterGroup">
      <path value="DeviceComponent.parameterGroup" />
      <comment value="Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.&#xD;&#xA;&#xD;&#xA;This information is not available by protocol from the PHD and its use is up to the application." />
    </element>
    <element id="DeviceComponent.measurementPrinciple">
      <path value="DeviceComponent.measurementPrinciple" />
      <comment value="This information is not available fron PHD devices by protocol. Its use is up to the implementation." />
    </element>
    <element id="DeviceComponent.productionSpecification">
      <path value="DeviceComponent.productionSpecification" />
      <definition value="The production specification such as component revision, serial number, etc. For the 11073 20601 Personal Health Device, the production specification entries come from the Production-Specification, System-Model, and Reg-Cert-Data-List attributes. There will be one productionSpecification entry for each item to be reported." />
      <comment value="All the PHD productionSpecification entries are strings and have IEEE 11073-10101 codes that define which production specification the string represents. Compliant PHDs will always have at least some entries for this element. If the PHD reports one or more such entries, they shall be recorded here. However, to allow the mapping of naughty proprietary devices, this element is made technically optional." />
    </element>
    <element id="DeviceComponent.productionSpecification.specType">
      <path value="DeviceComponent.productionSpecification.specType" />
      <min value="1" />
    </element>
    <element id="DeviceComponent.productionSpecification.specType.coding">
      <path value="DeviceComponent.productionSpecification.specType.coding" />
      <slicing>
        <discriminator>
          <type value="value" />
          <path value="system" />
        </discriminator>
        <ordered value="true" />
        <rules value="open" />
      </slicing>
      <min value="1" />
    </element>
    <element id="DeviceComponent.productionSpecification.specType.coding:11073Type">
      <path value="DeviceComponent.productionSpecification.specType.coding" />
      <sliceName value="11073Type" />
      <short value="The 11073-10101 code" />
      <definition value="The 11073-10101 code defining what the productionSpec is" />
      <comment value="11073 10101 codes have been defined for the Production-Specification and System-Model sub entries for use in V2 messaging. Though FHIR has provided its own set of codes based upon the names of the 11073-* Production-Specification.spec-type entry, the 11073-10101 codes are used since they are ubiquitous in these PHD-related profiles and it helps accelerate the acceptance of the MDC coding system in HL7." />
      <min value="1" />
      <max value="1" />
    </element>
    <element id="DeviceComponent.productionSpecification.specType.coding.system">
      <path value="DeviceComponent.productionSpecification.specType.coding.system" />
      <short value="Specifies IEEE 11073 10101" />
      <definition value="Identifies the IEEE 11073 10101 coding system" />
      <comment value="These codes are not seen on the wire between the PHD and the PHG. They are seen on the wire in PCD-01 messages." />
      <min value="1" />
      <fixedUri value="urn:iso:std:iso:11073:10101" />
    </element>
    <element id="DeviceComponent.productionSpecification.specType.coding.code">
      <path value="DeviceComponent.productionSpecification.specType.coding.code" />
      <short value="actual code" />
      <definition value="The 32 bit code identifying what the string in the DeviceComponent.productionSpecification.productionSpec element is." />
      <comment value="The currently defined codes used in this element are as follows:&#xD;&#xA;&#xD;&#xA;FIELD                                 CODE                  reference identifier&#xD;&#xA;------------------------------------------------------------------------------------&#xD;&#xA;Model number                 531969            MDC_ID_MODEL_NUMBER&#xD;&#xA;Manufacturer name         531970            MDC_ID_MODEL_MANUFACTURER&#xD;&#xA;                  The above come from the System-Model attribute&#xD;&#xA;&#xD;&#xA;Unspecified                      531971            MDC_ID_PROD_SPEC_UNSPECIFIED&#xD;&#xA;Serial number                  531972            MDC_ID_PROD_SPEC_SERIAL&#xD;&#xA;Part number                     531973            MDC_ID_PROD_SPEC_PART&#xD;&#xA;Hardware revision            531974            MDC_ID_PROD_SPEC_HW&#xD;&#xA;Software revision             531975            MDC_ID_PROD_SPEC_SW&#xD;&#xA;Firmware revision            531976            MDC_ID_PROD_SPEC_FW&#xD;&#xA;Protocol                           531977            MDC_ID_PROD_SPEC_PROTOCOL&#xD;&#xA;Global Medical Device&#xD;&#xA;Nomenclature (GMDN)    531978           MDC_ID_PROD_SPEC_GMDN&#xD;&#xA;                   The above come from the Production-Specification attribute&#xD;&#xA;&#xD;&#xA;Continua version              532352           MDC_REG_CERT_DATA_CONTINUA_VERSION&#xD;&#xA;                    The above comes from the Continua Reg-Cert-Data-List attribute&#xD;&#xA;&#xD;&#xA;There may be more fields added in future versions of the 10101 specification." />
      <requirements value="Need to identify what the reported string value represents" />
      <min value="1" />
    </element>
    <element id="DeviceComponent.productionSpecification.specType.coding.display">
      <extension url="http://hl7.org/fhir/StructureDefinition/elementdefinition-translatable">
        <valueBoolean value="true" />
      </extension>
      <path value="DeviceComponent.productionSpecification.specType.coding.display" />
      <definition value="A human readable display descrbing the meaning of the code." />
      <comment value="This element should contain the reference identfier for the reported code." />
    </element>
    <element id="DeviceComponent.productionSpecification.specType.coding:fhirCoding">
      <path value="DeviceComponent.productionSpecification.specType.coding" />
      <sliceName value="fhirCoding" />
      <short value="The IEEE concept in the DeviceSpecificationSpecType coding system" />
      <definition value="The IEEE concept defined in the 11073Type coding element expressed in the DeviceSpecificationSpecType coding system." />
      <comment value="FHIR requires this element to be present IF the production specification being reported is included in the DeviceSpecificationSpecType value set. Currently that is all the possible entries defined in the IEEE 11073 ProductionSpecification attribute. These codes and entries are as follows:&#xD;&#xA;Code                      Description&#xD;&#xA;unspecified            Unspecified Production Specification &#xD;&#xA;serial-number        Serial Number&#xD;&#xA;part-number          Part Number &#xD;&#xA;hardware-revision  Hardware Revision &#xD;&#xA;software-revision   Software Revision &#xD;&#xA;firmware-revision   Firmware Revision &#xD;&#xA;protocol-revision    Protocol Revision &#xD;&#xA;gmdn                      Global Medical Device Nomencalture" />
      <requirements value="Besides satisfying a system requirement, including these values supports searches for DeviceComponents based upon the DeviceSpecificationSpecType codes. Of course, as of 3.0.1 searches on the DeviceComponent.productionSpecification are not supported but this is to change in the future." />
      <max value="1" />
    </element>
    <element id="DeviceComponent.productionSpecification.specType.coding:fhirCoding.system">
      <path value="DeviceComponent.productionSpecification.specType.coding.system" />
      <min value="1" />
      <fixedUri value="http://hl7.org/fhir/specification-type" />
    </element>
    <element id="DeviceComponent.productionSpecification.specType.coding:fhirCoding.code">
      <path value="DeviceComponent.productionSpecification.specType.coding.code" />
      <definition value="A symbol in the syntax defined by the DeviceSpecificationSpecType system. " />
      <comment value="FHIR requires this code if the specType being coded is a member of this value set." />
      <min value="1" />
    </element>
    <element id="DeviceComponent.productionSpecification.specType.coding:alternativeCoding">
      <path value="DeviceComponent.productionSpecification.specType.coding" />
      <sliceName value="alternativeCoding" />
    </element>
    <element id="DeviceComponent.productionSpecification.specType.coding:alternativeCoding.system">
      <path value="DeviceComponent.productionSpecification.specType.coding.system" />
      <min value="1" />
    </element>
    <element id="DeviceComponent.productionSpecification.productionSpec">
      <path value="DeviceComponent.productionSpecification.productionSpec" />
      <min value="1" />
    </element>
    <element id="DeviceComponent.languageCode">
      <path value="DeviceComponent.languageCode" />
      <comment value="Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.&#xD;&#xA;This infomration is not available by protocol from the PHD and its use is up to the application" />
    </element>
  </differential>
</StructureDefinition>

name : phdParentDeviceComponent

{

}

<name value="phdParentDeviceComponent" />