Skip to content

Commit ed7007b

Browse files
ErikMollErikMoll
authored
Merge pull request #81 from HL7/ACOM-GHS-support
mapping for metric
2 parents eb40e33 + de761e8 commit ed7007b

2 files changed

Lines changed: 29 additions & 12 deletions

File tree

‎input-cache/schemas/R5/fhir-single.xsd‎

Lines changed: 18 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@
4747
POSSIBILITY OF SUCH DAMAGE.
4848

4949

50-
Generated on Wed, Jul 30, 2025 23:11+0000 for FHIR v6.0.0-ballot2
50+
Generated on Mon, Aug 11, 2025 12:53+0000 for FHIR v6.0.0-ballot2
5151
-->
5252
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="http://hl7.org/fhir" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xml="http://www.w3.org/XML/1998/namespace" targetNamespace="http://hl7.org/fhir" elementFormDefault="qualified" version="6.0.0-ballot2">
5353
<!-- Note: When using this schema with some tools, it may also be necessary to declare xmlns:xml="http://www.w3.org/XML/1998/namespace", however this causes performance issues with other tools and thus is not in the base schemas. -->
@@ -30434,12 +30434,12 @@ The actual author of the section when it is not the author of the composition. I
3043430434
</xs:element>
3043530435
<xs:element name="carrierAIDC" minOccurs="0" maxOccurs="1" type="base64Binary">
3043630436
<xs:annotation>
30437-
<xs:documentation xml:lang="en">The full UDI carrier of the Automatic Identification and Data Capture (AIDC) technology representation as printed on the packaging of the device - e.g., a barcode or RFID. Because of limitations on character sets in XML and the need to round-trip JSON data through XML, AIDC Formats *SHALL* be base64 encoded.</xs:documentation>
30437+
<xs:documentation xml:lang="en">The full UDI carrier of the Automatic Identification and Data Capture (AIDC) technology representation as printed on the packaging of the device - e.g., a barcode , 2D Matrix, or RFID. Some AIDC representations contain non-printable characters and cannot be represented in a string format. For this reason, AIDC format SHALL be base64Binary encoded.</xs:documentation>
3043830438
</xs:annotation>
3043930439
</xs:element>
3044030440
<xs:element name="carrierHRF" minOccurs="0" maxOccurs="1" type="string">
3044130441
<xs:annotation>
30442-
<xs:documentation xml:lang="en">The full UDI carrier as the human readable form (HRF) representation of the barcode string as printed on the packaging of the device.</xs:documentation>
30442+
<xs:documentation xml:lang="en">The full UDI carrier as the human readable form (HRF) representation as printed on the packaging of the device.</xs:documentation>
3044330443
</xs:annotation>
3044430444
</xs:element>
3044530445
<xs:element name="entryType" minOccurs="0" maxOccurs="1" type="UDIEntryType">
@@ -31182,7 +31182,7 @@ The actual author of the section when it is not the author of the composition. I
3118231182
</xs:element>
3118331183
<xs:element name="udiDeviceIdentifier" type="DeviceDefinition.UdiDeviceIdentifier" minOccurs="0" maxOccurs="unbounded">
3118431184
<xs:annotation>
31185-
<xs:documentation xml:lang="en">Unique device identifier (UDI) assigned to device label or package. Note that the Device may include multiple udiCarriers as it either may include just the udiCarrier for the jurisdiction it is sold, or for multiple jurisdictions it could have been sold.</xs:documentation>
31185+
<xs:documentation xml:lang="en">The Device Identifier (DI) portion of the Unique Device Identifier (UDI) placed on a device label or package. Also known as UDI-DI. Note that the DeviceDefinition may include multiple UDI-DIs if it is sold in multiple jurisdictions.</xs:documentation>
3118631186
</xs:annotation>
3118731187
</xs:element>
3118831188
<xs:element name="regulatoryIdentifier" type="DeviceDefinition.RegulatoryIdentifier" minOccurs="0" maxOccurs="unbounded">
@@ -31306,6 +31306,11 @@ The actual author of the section when it is not the author of the composition. I
3130631306
<xs:documentation xml:lang="en">Indicates where and when the device is available on the market.</xs:documentation>
3130731307
</xs:annotation>
3130831308
</xs:element>
31309+
<xs:element name="deviceIdentifierSystem" minOccurs="0" maxOccurs="1" type="uri">
31310+
<xs:annotation>
31311+
<xs:documentation xml:lang="en">Establishes the namespace for the issuing agency's system (e.g, GS1's GTIN, ICCBBA's ISBT-128) used to create the device identifier.</xs:documentation>
31312+
</xs:annotation>
31313+
</xs:element>
3130931314
</xs:sequence>
3131031315
</xs:extension>
3131131316
</xs:complexContent>
@@ -31358,6 +31363,11 @@ The actual author of the section when it is not the author of the composition. I
3135831363
<xs:documentation xml:lang="en">The jurisdiction to which the deviceIdentifier applies.</xs:documentation>
3135931364
</xs:annotation>
3136031365
</xs:element>
31366+
<xs:element name="deviceIdentifierSystem" minOccurs="0" maxOccurs="1" type="uri">
31367+
<xs:annotation>
31368+
<xs:documentation xml:lang="en">Establishes the namespace for the issuing agency's system (e.g, GS1's GTIN, ICCBBA's ISBT-128) used to create the device identifier.</xs:documentation>
31369+
</xs:annotation>
31370+
</xs:element>
3136131371
</xs:sequence>
3136231372
</xs:extension>
3136331373
</xs:complexContent>
@@ -59972,7 +59982,7 @@ Deceased patients may also be marked as inactive for the same reasons, but may b
5997259982
<xs:documentation xml:lang="en">The performer of the processing of the specimen.</xs:documentation>
5997359983
</xs:annotation>
5997459984
</xs:element>
59975-
<xs:element name="device" minOccurs="0" maxOccurs="1" type="Reference">
59985+
<xs:element name="device" minOccurs="0" maxOccurs="1" type="CodeableReference">
5997659986
<xs:annotation>
5997759987
<xs:documentation xml:lang="en">The device used in the processing of the specimen.</xs:documentation>
5997859988
</xs:annotation>
@@ -60001,7 +60011,7 @@ Deceased patients may also be marked as inactive for the same reasons, but may b
6000160011
<xs:complexContent>
6000260012
<xs:extension base="BackboneElement">
6000360013
<xs:sequence>
60004-
<xs:element name="device" minOccurs="1" maxOccurs="1" type="Reference">
60014+
<xs:element name="device" minOccurs="1" maxOccurs="1" type="CodeableReference">
6000560015
<xs:annotation>
6000660016
<xs:documentation xml:lang="en">The device resource for the the container holding the specimen. If the container is in a holder then the referenced device will point to a parent device.</xs:documentation>
6000760017
</xs:annotation>
@@ -64099,7 +64109,7 @@ Deceased patients may also be marked as inactive for the same reasons, but may b
6409964109
<xs:documentation xml:lang="en">The current status of the task.</xs:documentation>
6410064110
</xs:annotation>
6410164111
</xs:element>
64102-
<xs:element name="statusReason" minOccurs="0" maxOccurs="1" type="CodeableReference">
64112+
<xs:element name="statusReason" minOccurs="0" maxOccurs="unbounded" type="CodeableReference">
6410364113
<xs:annotation>
6410464114
<xs:documentation xml:lang="en">An explanation as to why this task is held, failed, was refused, etc.</xs:documentation>
6410564115
</xs:annotation>
@@ -67997,10 +68007,7 @@ Deceased patients may also be marked as inactive for the same reasons, but may b
6799768007
</xs:element>
6799868008
<xs:element name="value" minOccurs="1" maxOccurs="1" type="string">
6799968009
<xs:annotation>
68000-
<xs:documentation xml:lang="en">ValueSet.compose.include.filter.value is represented as a string, and the string value must be one of the three types below:
68001-
When the filter operation (ValueSet.compose.include.filter.op) is equal to &quot;regex&quot;, the value (ValueSet.compose.include.filter.value) is a regex expression. This is used to match string values (including integer and decimal, if necessary).
68002-
When the filter operation (ValueSet.compose.include.filter.op) is equal to &quot;exists&quot;, the value (ValueSet.compose.include.filter.value) is a boolean and must be equal to &quot;true&quot; or &quot;false&quot;.
68003-
For all other filter operations (ValueSet.compose.include.filter.op) the value (ValueSet.compose.include.filter.value) represents a code.</xs:documentation>
68010+
<xs:documentation xml:lang="en">ValueSet.compose.include.filter.value is represented as a string, and the string value must be [as described](valueset.html#filter-values).</xs:documentation>
6800468011
</xs:annotation>
6800568012
</xs:element>
6800668013
</xs:sequence>

‎input/fsh/StructureDefinition.PhdDeviceMetric.fsh‎

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,4 +33,14 @@ Description: "Profile for the DeviceMetric for a PHD"
3333
* ^short = "No reference to a parent device in PHD. PHDs are not part of a device hierarchy."
3434
* extension contains http://hl7.org/fhir/uv/phd/StructureDefinition/Accuracy named Accuracy 0..1
3535
* extension contains http://hl7.org/fhir/uv/phd/StructureDefinition/Confidence95 named Confidence95 0..1
36-
* extension contains http://hl7.org/fhir/uv/phd/StructureDefinition/SimpleAlerting named SimpleAlerting 0..1
36+
* extension contains http://hl7.org/fhir/uv/phd/StructureDefinition/SimpleAlerting named SimpleAlerting 0..1
37+
38+
Mapping: IEEE-11073-10206-PhdDeviceMetric
39+
Title: "IEEE-11073-10206 ACOM to FHIR PhdDeviceMetric"
40+
Source: PhdDeviceMetric
41+
Target: "https://sagroups.ieee.org/11073/phd-wg"
42+
* -> "ACOM"
43+
* type.coding.code -> "SystemInfo.observation-type-list[i]"
44+
* type.coding.system -> "urn:iso:std:iso:11073:10101"
45+
* unit -> "UCUM unit used for SystemInfo.observation-type-list[i] observations"
46+
* category -> "filled in when this can be derived from the SystemInfo.observation-type-list[i]"

0 commit comments

Comments
 (0)