From de761e8c0be81aece9fdc89365a72aa7cba3f25a Mon Sep 17 00:00:00 2001 From: Erik Moll Date: Thu, 14 Aug 2025 13:15:59 +0200 Subject: [PATCH] mapping for metric --- input-cache/schemas/R5/fhir-single.xsd | 29 ++++++++++++------- .../StructureDefinition.PhdDeviceMetric.fsh | 12 +++++++- 2 files changed, 29 insertions(+), 12 deletions(-) diff --git a/input-cache/schemas/R5/fhir-single.xsd b/input-cache/schemas/R5/fhir-single.xsd index 6091e0a..a87244d 100644 --- a/input-cache/schemas/R5/fhir-single.xsd +++ b/input-cache/schemas/R5/fhir-single.xsd @@ -47,7 +47,7 @@ POSSIBILITY OF SUCH DAMAGE. - Generated on Wed, Jul 30, 2025 23:11+0000 for FHIR v6.0.0-ballot2 + Generated on Mon, Aug 11, 2025 12:53+0000 for FHIR v6.0.0-ballot2 --> @@ -30434,12 +30434,12 @@ The actual author of the section when it is not the author of the composition. I - 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. + 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. - The full UDI carrier as the human readable form (HRF) representation of the barcode string as printed on the packaging of the device. + The full UDI carrier as the human readable form (HRF) representation as printed on the packaging of the device. @@ -31182,7 +31182,7 @@ The actual author of the section when it is not the author of the composition. I - 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. + 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. @@ -31306,6 +31306,11 @@ The actual author of the section when it is not the author of the composition. I Indicates where and when the device is available on the market. + + + Establishes the namespace for the issuing agency's system (e.g, GS1's GTIN, ICCBBA's ISBT-128) used to create the device identifier. + + @@ -31358,6 +31363,11 @@ The actual author of the section when it is not the author of the composition. I The jurisdiction to which the deviceIdentifier applies. + + + Establishes the namespace for the issuing agency's system (e.g, GS1's GTIN, ICCBBA's ISBT-128) used to create the device identifier. + + @@ -59972,7 +59982,7 @@ Deceased patients may also be marked as inactive for the same reasons, but may b The performer of the processing of the specimen. - + The device used in the processing of the specimen. @@ -60001,7 +60011,7 @@ Deceased patients may also be marked as inactive for the same reasons, but may b - + 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. @@ -64099,7 +64109,7 @@ Deceased patients may also be marked as inactive for the same reasons, but may b The current status of the task. - + An explanation as to why this task is held, failed, was refused, etc. @@ -67997,10 +68007,7 @@ Deceased patients may also be marked as inactive for the same reasons, but may b - ValueSet.compose.include.filter.value is represented as a string, and the string value must be one of the three types below: -When the filter operation (ValueSet.compose.include.filter.op) is equal to "regex", the value (ValueSet.compose.include.filter.value) is a regex expression. This is used to match string values (including integer and decimal, if necessary). -When the filter operation (ValueSet.compose.include.filter.op) is equal to "exists", the value (ValueSet.compose.include.filter.value) is a boolean and must be equal to "true" or "false". -For all other filter operations (ValueSet.compose.include.filter.op) the value (ValueSet.compose.include.filter.value) represents a code. + ValueSet.compose.include.filter.value is represented as a string, and the string value must be [as described](valueset.html#filter-values). diff --git a/input/fsh/StructureDefinition.PhdDeviceMetric.fsh b/input/fsh/StructureDefinition.PhdDeviceMetric.fsh index 865971d..09a9b63 100644 --- a/input/fsh/StructureDefinition.PhdDeviceMetric.fsh +++ b/input/fsh/StructureDefinition.PhdDeviceMetric.fsh @@ -33,4 +33,14 @@ Description: "Profile for the DeviceMetric for a PHD" * ^short = "No reference to a parent device in PHD. PHDs are not part of a device hierarchy." * extension contains http://hl7.org/fhir/uv/phd/StructureDefinition/Accuracy named Accuracy 0..1 * extension contains http://hl7.org/fhir/uv/phd/StructureDefinition/Confidence95 named Confidence95 0..1 -* extension contains http://hl7.org/fhir/uv/phd/StructureDefinition/SimpleAlerting named SimpleAlerting 0..1 \ No newline at end of file +* extension contains http://hl7.org/fhir/uv/phd/StructureDefinition/SimpleAlerting named SimpleAlerting 0..1 + +Mapping: IEEE-11073-10206-PhdDeviceMetric +Title: "IEEE-11073-10206 ACOM to FHIR PhdDeviceMetric" +Source: PhdDeviceMetric +Target: "https://sagroups.ieee.org/11073/phd-wg" +* -> "ACOM" +* type.coding.code -> "SystemInfo.observation-type-list[i]" +* type.coding.system -> "urn:iso:std:iso:11073:10101" +* unit -> "UCUM unit used for SystemInfo.observation-type-list[i] observations" +* category -> "filled in when this can be derived from the SystemInfo.observation-type-list[i]" \ No newline at end of file