8.5 Design Guidelines
8.5.3 Data Guidelines
Table 8-6
General Data Payload Guidelines
Name
Description
Reqt Map
Comments
WAN_Data_Standard Continua WAN service and client components shall conform to the IHE Patient Care Devices Technical Framework Revision 2.0 except where these
constraints conflict with this document WAN_Interface_ Protocol_Data, WAN_Interfaces_ Data_Standard_F ormat, WAN_Interfaces_ Data_Meta_Data
There are no known conflicts
WAN_Data_Standard_Cons
traints Continua WAN service and client component HL7 message payloads shall conform to the constraints defined in Appendix K WAN_Data_Standard_Enco
ding Continua WAN client and service component shall use the HL7 v2.6 EDI encoding and shall not use the HL7 v2.6 XML encoding
The PCD TF allows both EDI and XML encoding
WAN_Data_Coding_MDC Continua WAN client component observations shall use the Medical Device Communication (MDC) coding system for all Observation Identifiers (OBX-3, OBX-20)
WAN_Interfaces_
Design Guidelines Version 2013
147 Modified on: August 6, 2013
Copying or other form of reproduction or redistribution of these works to unauthorized entities is strictly prohibited.
Name
Description
Reqt Map
Comments
WAN_Data_Measurement_
Units Continua WAN client component observations shall use the Medical Device Communication (MDC) coding system for all non-empty Units (OBX-6)
WAN_Interfaces_
Data_Meta_Data Minimal translation
WAN_Data_Minimize_Conv
ention Continua WAN Client components should terminate all Observation Result segments after their last non-empty sequence WAN_Data_Authoring_Devi
ce For observations which originate from a Continua PAN or LAN device, the Continua WAN client component shall include an MDS-level OBX segment with an Observation Identifier equal to the MDC Device Specialization Profile reported by the PAN or LAN device
WAN_Interfaces_ Data_Quality_In dications
If the PAN or LAN Device’s System-Type attribute is set, this value must be used as the OBX-3 of the MDS- level OBX
If System-Type-Spec- List contains a single value and System-Type is not valued, this value must be reported as the OBX-3 of the MDS-level OBX If System-Type-Spec- List contains multiple values and System- Type is not valued, OBX-3 of the MDS-level OBX must be set to 528384^MDC_DEV_SP EC_PROFILE_HYDRA^ MDC and the System- Type-Spec-List attribute must be reported as a separate Metric of the MDS-level OBX
WAN_Data_Authoring_Devi
ce_Identity For observations which originate from a Continua PAN or LAN device, the Continua WAN client component shall include the EUI-64 SystemId of the originating Continua PAN or LAN device in the
Equipment Identifier field of the MDS-level OBX (OBX- 18)
WAN_Interfaces_ Data_Quality_In dications
The identifier should be sent in the form “0123456789ABCDEF^ EUI-64” with no hyphens included in the string identifier
subcomponent as specified in the IHE PCD Technical Framework
Version 2013 Design Guidelines
Name
Description
Reqt Map
Comments
WAN_Data_Authoring_Devi
ce_Regulatory_Information For observations which originate from a Continua PAN or LAN device, the Continua WAN client component shall include all regulatory information reported by the PAN or LAN device as a subcomponent (METRIC) of the MDS-level OBX for the originating device
WAN_Interfaces_ Data_Quality_In dications
Continua-certified PAN and LAN devices must be passed using the Regulation-
Certification-Auth-Body Metric OBX with a value including 2^auth-body-
continua(2), along with the Regulation-
Certification-Continua- * Metrics listed in Appendix J.2
WAN_Data_device_regulat
ory_information WAN client components shall include their regulatory information as a subcomponent (METRIC) of the AHD-level OBX. The mapping is described in Table J-1
WAN_Interfaces_ Data_Quality_In dications
Continua certified AHDs shall include their own regulatory information in a special set of zero- level OBX segments. The complete list of required and conditionally required information is given in Appendix J.1 WAN_Data_Authoring_Devi ce_Encoding_MDS_Attribut es
When encoding MDS object attributes, the Continua WAN client component shall use the encodings shown in Appendix J.1.1 of this document Ensure all MDS attribute encoding is aligned WAN_Data_Authoring_Devi ce_Encoding_Algorithm_Sp ecific
For observations which originate from a Continua PAN or LAN Certified Device Class defined in this document, the WAN client component shall use the device specific encoding methodology defined in Appendix J
Use targeted encoding whenever possible
WAN_Data_Authoring_Devi ce_Encoding_Algorithm_Ge neric
For observations which do not originate from a Continua PAN or LAN Certified Device Class defined in this document, the WAN client component should use the mapping guidance from the specific encoding methodology defined in Appendix J and, otherwise, should follow the generic encoding methodology defined in Appendix I.3
This guideline covers non-certified devices and Continua device specialization defined after the creation of this document
Design Guidelines Version 2013
149 Modified on: August 6, 2013
Copying or other form of reproduction or redistribution of these works to unauthorized entities is strictly prohibited.
Name
Description
Reqt Map
Comments
WAN_Data_Authoring_Devi
ce_Encoding_Containment For observations which originate from a Continua PAN or LAN device, the Continua WAN client component shall use the specified containment notation in OBX-4
Maintain relationships of measurements
WAN_Data_Authoring_Devi
ce_Encoding_Timestamp The Continua WAN client component should report all time values in MSH-7, OBR-7, OBR-8, and OBX-14 as UTC or UTC coordinated values expressed as an HL7 date/time (DTM) data type
WAN_Interfaces_ Data_Timestamp _Accuracy, WAN_Interface_ DST_TZ
It is imperative that all measurements can be correlated to a single comprehensive timeline for proper, safe analysis and usage. UTC values are reported using the +0000 time zone suffix WAN_Data_Authoring_Devi
ce_Encoding_Time_Abs In order to report observations originating from a Continua PAN or LAN device with absolute time, Continua WAN client components shall include an MDC_ATTR_TIME_ABS OBX as a child (METRIC) of the corresponding MDS- level OBX with the corresponding UTC time in OBX-14 WAN_Interfaces_ Data_Time, WAN_Interfaces_ Data_Time_Resol ution
This will ensure traceability to the originally reported time
WAN_Data_Authoring_Devi
ce_Encoding_Time_Rel In order to report observations originating from a Continua PAN or LAN device with relative time, Continua WAN client components shall include an
MDC_ATTR_TIME_STAMP_R EL OBX as a child (FACET) of the corresponding Metric observation WAN_Interfaces_ Data_Time, WAN_Interfaces_ Data_Time_Resol ution In IEEE 11073-20601, relative-time is reported in 1/8 of a millisecond (125 us) which must be translated to a valid MDC unit such as MDC_DIM_MILLI_SEC on the WAN interface
WAN_Data_Authoring_Devi ce_Encoding_Time_Rel_Hir es
In order to report observations originating from a Continua PAN or LAN device with hi resolution relative time, Continua WAN client components shall include an
MDC_ATTR_TIME_STAMP_R EL_HI_RES OBX as a child (FACET) of the corresponding Metric observation WAN_Interfaces_ Data_Time, WAN_Interfaces_ Data_Time_Resol ution
Version 2013 Design Guidelines
Name
Description
Reqt Map
Comments
WAN_Data_Authoring_Devi ce_Encoding_Nomenclature _Translation
Continua WAN client components shall adjust all nomenclature values that use the “_X” indicator in the name to the corresponding correct base value without the “_X” indicator
Ensure all
nomenclature usage is aligned
This form of the unit code REFID values is called “unity scaling” because there is no SI prefix used
WAN_Data_Authoring_Devi
ce_Encoding_Bit_Flags When encoding bit flag values (such as 11073- 20601 Enumeration fields), the Continua WAN client component shall use the format of
<bitValue>^<bitName>(<b itPosition>)
Where:
bitValue: <0 or 1> bitName: the normative ASN.1 name for the bit bitPosition: the normative position of the bit in the field
The values for bitValue and bitPosition shall be always present and the value for bitName should be present
Ensure all bit usage is aligned
(For example: Enumeration bit fields)
WAN_Data_Authoring_Devi
ce_Encoding_MDC_Codes When encoding MDC codes using the HL7 CWE data type, Continua WAN client components shall use the format of
<refIdValue>^<refIdName ><refIdCodeSystem> Where:
refIdValue: is the 32 bit integer that corresponds to the unique code point refIdName: the normative nomenclature name for the unique code point
refIdCodeSystem: the value shall always be “MDC” The values for refIdValue and refIdCodeSystem shall always be present and the value for refIdName should be present
Ensure all
nomenclature usage is aligned
Design Guidelines Version 2013
151 Modified on: August 6, 2013
Copying or other form of reproduction or redistribution of these works to unauthorized entities is strictly prohibited.