From d993bf3ee04820d48878dcbef93ce156864ecf28 Mon Sep 17 00:00:00 2001 From: Erik Moll Date: Tue, 29 Jul 2025 14:45:34 +0200 Subject: [PATCH] another update of the pub request & editorials --- FHIR-phd.xml | 4 ++-- input-cache/schemas/R5/fhir-single.xsd | 4 ++-- input/PhdImplementationGuide.xml | 11 ++++++++--- input/fsh/StructureDefinition.PhdBaseObservation.fsh | 8 ++++---- ...uctureDefinition.PhdCompoundNumericObservation.fsh | 2 +- .../StructureDefinition.PhdCompoundObservation.fsh | 2 +- input/fsh/StructureDefinition.PhgDevice.fsh | 2 +- input/fsh/ValueSet.ASN1ClockBits.fsh | 2 +- input/ignoreWarnings.txt | 6 +++--- .../StructureDefinition-PhdBaseObservation-notes.md | 4 ++-- ...Definition-PhdCodedEnumerationObservation-intro.md | 2 +- ...eDefinition-PhdCompoundNumericObservation-intro.md | 2 +- ...eDefinition-PhdCompoundNumericObservation-notes.md | 2 +- ...tructureDefinition-PhdCompoundObservation-intro.md | 2 +- ...tructureDefinition-PhdCompoundObservation-notes.md | 2 +- input/pagecontent/DIMtoFHIRMapping.md | 8 ++++---- input/pagecontent/Glossary.md | 1 + input/pagecontent/ProfilesOverview.md | 2 +- publication-request.json | 4 ++-- 19 files changed, 38 insertions(+), 32 deletions(-) diff --git a/FHIR-phd.xml b/FHIR-phd.xml index af363b0..d50e60e 100644 --- a/FHIR-phd.xml +++ b/FHIR-phd.xml @@ -1,7 +1,7 @@ - + - + diff --git a/input-cache/schemas/R5/fhir-single.xsd b/input-cache/schemas/R5/fhir-single.xsd index c1a3336..13bdc8f 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 Sat, Jul 26, 2025 01:41+0000 for FHIR v6.0.0-ballot2 + Generated on Tue, Jul 29, 2025 04:15+0000 for FHIR v6.0.0-ballot2 --> @@ -59787,7 +59787,7 @@ Deceased patients may also be marked as inactive for the same reasons, but may b - Id for specimen. + Identifiers used for specimen identification. These could include but are not limited to identifiers generated upon collection, accessioning, or other reasons for labeling a specimen. diff --git a/input/PhdImplementationGuide.xml b/input/PhdImplementationGuide.xml index 39c0b80..b9cf4a7 100644 --- a/input/PhdImplementationGuide.xml +++ b/input/PhdImplementationGuide.xml @@ -43,7 +43,7 @@ In this example there are only xml structure definitions, value sets, code syste xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://hl7.org/fhir/src-generated/schemas/fhir-single.xsd"> - + <status value="active"/> @@ -244,7 +244,7 @@ In this example there are only xml structure definitions, value sets, code syste <reference> <reference value="ValueSet/ASN1MeasurementBits"/> </reference> - <description value="Value set for those Asn1ToHL7 codes whose source is a measurement attribute; one of the Enum-observed-value attributes."/> + <description value="Value set for those Asn1ToHL7 codes whose source is a measurement attribute."/> <exampleBoolean value="false"/> </resource> <!-- these value sets were missing --> @@ -450,7 +450,7 @@ In this example there are only xml structure definitions, value sets, code syste <reference value="Device/phd-711000FEFF5F49B0.B0495F001071"/> </reference> <name value="Example of a Blood Pressure PHD"/> - <description value="This example maps the MDS data from a Blood Pressure PHD. This device did not report Reg-Cert-Data-List information." /> + <description value="This example maps the System Information data from a Blood Pressure PHD. This device did not report Reg-Cert-Data-List information." /> <exampleCanonical value="http://hl7.org/fhir/uv/phd/StructureDefinition/PhdDevice"/> </resource> <resource> @@ -626,6 +626,11 @@ In this example there are only xml structure definitions, value sets, code syste <parameter> <code value="special-url"/> <value value="http://terminology.hl7.org/CodeSystem/ASN1ToHL7"/> + </parameter> + <parameter> + <code value="special-url"/> + <value value="http://terminology.hl7.org/ValueSet/ASN1ClockBits"/> </parameter> </definition> + </ImplementationGuide> diff --git a/input/fsh/StructureDefinition.PhdBaseObservation.fsh b/input/fsh/StructureDefinition.PhdBaseObservation.fsh index 7b2120f..d5a73c9 100644 --- a/input/fsh/StructureDefinition.PhdBaseObservation.fsh +++ b/input/fsh/StructureDefinition.PhdBaseObservation.fsh @@ -52,8 +52,8 @@ Description: "Common base profile with the elements that are common to the PHD I * ^slicing.rules = #open * identifier contains conditionalCreate 0..1 * identifier[conditionalCreate] ^short = "Unique identifier of this measurement for a given patient and device" - * ^definition = "An identifier created from a combination of the measurement parameters like sensor timestamp, type code, unit code, patient and device identifiers, and selected elements of any component elements." - * ^comment = "This value is used in the conditional create to prevent data duplication. PHDs will often re-send already sent data for a variety of reasons. This element is required unless the metric measurement contains no timestamp or is a measurement containing a timestamp that is real time. By real time the timestamp reported by the PHD must be later than the current time reported by the PHD before any measurements are received. There might be other means to ascertain whether the data is real time. Temporarily stored data from IEEE 11073-10206 compliant devices, which are required to be deleted the data after sending, can be considered real time. An example of this are temporarily stored observations from a device implementing the Bluetooth SIG GHS profile or implementing another Bluetooth SIG medical sensor device profile." + * ^definition = "An identifier created from a combination of the measurement parameters like sensor timestamp, type code, unit code, patient and device identifier." + * ^comment = "This value is used in the conditional create to prevent data duplication. PHDs will often re-send already sent data for a variety of reasons. This element is recommended unless the observation contains no timestamp or is a measurement containing a timestamp that is real time. By real time the timestamp reported by the PHD must be later than the current time reported by the PHD before any measurements are received. There might be other means to ascertain whether the data is real time. Temporarily stored data from IEEE 11073-10206 compliant devices, which are required to be deleted the data after sending, can be considered real time. An example of this are temporarily stored observations from a device implementing the Bluetooth SIG GHS profile or implementing another Bluetooth SIG medical sensor device profile." * ^requirements = "Allows observations to be distinguished in a selective enough manner to prevent resource duplication." * type ..0 * system = "http://hl7.org/fhir/uv/phd/StructureDefinition/PhdBaseObservation" (exactly) @@ -68,7 +68,7 @@ Description: "Common base profile with the elements that are common to the PHD I * ^short = "Reference to the patient or the PhdDevice that is the subject of the observation" * effective[x] 1.. * effective[x] only dateTime or Period - * ^definition = "The time or time-period the observed value is asserted as being true. It is a time period if a Measure-Active-Period (duration) attribute is part of the metric measurement sent by the PHD. Otherwise it is the timestamp sent by the PHD or the time of reception by the PHG if the PHD sent no timestamp." + * ^definition = "The time or time-period the observed value is asserted as being true. This can be a dateTime or a period. The value is based on the timestamp sent by the PHD or the time of reception by the PHG if the PHD sent no timestamp." * interpretation * coding ^slicing.discriminator[0].type = #value * ^slicing.discriminator[=].path = "system" @@ -90,7 +90,7 @@ Description: "Common base profile with the elements that are common to the PHD I * ^slicing.rules = #open * component contains supplementalTypesComponent 0..* * component[supplementalTypesComponent] ^short = "Supplemental Type: A further description of the measurement type." - * ^definition = "For each code contained in the Supplemental-Types attribute, a separate supplementalTypesComponent element is generated. The component is not generated if the attribute is absent or empty. The component shall be generated otherwise." + * ^definition = "For each code contained in the Supplemental-Types attribute, a separate component is generated. The component is not generated if the attribute is absent or empty. The component shall be generated otherwise." * ^comment = "A PHD may send a Supplemental-Types attribute as part of the measurement. This attribute consists of a set of MDC nomenclature codes. Each code describes an aspect of the measurement, such as MDC_MODALITY_SPOT in the pulse oximeter which indicates that the provided measurement is a stable average." // * code from $CodeableConcept11073MDC (required) * code = Mdc#68193 // from $CodeableConcept11073MDC (required) diff --git a/input/fsh/StructureDefinition.PhdCompoundNumericObservation.fsh b/input/fsh/StructureDefinition.PhdCompoundNumericObservation.fsh index 35e32ba..5d75e5e 100644 --- a/input/fsh/StructureDefinition.PhdCompoundNumericObservation.fsh +++ b/input/fsh/StructureDefinition.PhdCompoundNumericObservation.fsh @@ -18,7 +18,7 @@ Description: "Observations coming from a PHD where the measurement is a set of n compound 0..* * component[compound] ^short = "Compound numeric measurement entry components" * ^definition = "Each compoundComponent contains one of the N constituents of the compound measurement. These entries are NOT present if a Measurement-Status attribute indicates an error." - * ^comment = "A compound measurement is a measurement that requires more than one value to represent it, such as an acceleration which has an x, y, and z components. The Blood pressure is also represented as a compound measurement, containing systolic, diastolic and MAP components. One combines all the compound elements together to describe the measurement. The Metric-Id-List entry n and Compound-Basic/Simple-Nu-Observed-Value entry n are ordered such that the code that describes each entry n is computed from the partition of the Type attribute and the term code of the Metric-Id-List attribute. In the case of the Compound-Nu-Observed-Value, the term code comes from the Compound-Nu-Observed-Value.metric sub-component." + * ^comment = "A compound measurement is a measurement that requires more than one value to represent it, such as an acceleration which has an x, y, and z components. The Blood pressure is also represented as a compound measurement, containing systolic, diastolic and MAP components. One combines all the compound elements together to describe the measurement." * code from $MDCnotObject (required) * coding 1.. * ^slicing.discriminator[0].type = #value diff --git a/input/fsh/StructureDefinition.PhdCompoundObservation.fsh b/input/fsh/StructureDefinition.PhdCompoundObservation.fsh index dafa0d6..07f6329 100644 --- a/input/fsh/StructureDefinition.PhdCompoundObservation.fsh +++ b/input/fsh/StructureDefinition.PhdCompoundObservation.fsh @@ -17,7 +17,7 @@ Description: "Observations from a PHD where the measurement is a set of numbers measurement 0..* * component[measurement] ^short = "Compound measurement entry component" * ^definition = "Each compoundComponent contains one of the N constituents of the compound measurement. These entries are NOT present if a Measurement-Status attribute indicates an error." - * ^comment = "A compound measurement is a measurement that requires more than one value to represent it, such as an acceleration which has an x, y, and z components. The Blood pressure is also represented as a compound measurement, containing systolic, diastolic and MAP components. One combines all the compound elements together to describe the measurement. The Metric-Id-List entry n and Compound-Basic/Simple-Nu-Observed-Value entry n are ordered such that the code that describes each entry n is computed from the partition of the Type attribute and the term code of the Metric-Id-List attribute. In the case of the Compound-Nu-Observed-Value, the term code comes from the Compound-Nu-Observed-Value.metric sub-component." + * ^comment = "A compound measurement is a measurement that requires more than one value to represent it, such as an acceleration which has an x, y, and z components. The Blood pressure is also represented as a compound measurement, containing systolic, diastolic and MAP components. One combines all the compound elements together to describe the measurement." * code from http://hl7.org/fhir/uv/phd/ValueSet/MDCValueSet (required) * value[x] only Quantity or CodeableConcept or string or SampledData * valueQuantity diff --git a/input/fsh/StructureDefinition.PhgDevice.fsh b/input/fsh/StructureDefinition.PhgDevice.fsh index e8fea4a..b211d3b 100644 --- a/input/fsh/StructureDefinition.PhgDevice.fsh +++ b/input/fsh/StructureDefinition.PhgDevice.fsh @@ -134,7 +134,7 @@ Description: "Profile for the Device Resource for a PHG" * valueCode from http://hl7.org/fhir/uv/phd/ValueSet/ContinuaPHGInterfaces (extensible) * property[clockBitProperty] ^short = "Boolean Properties reported by the Clock" - * ^definition = "For each Boolean clock capability reported a property element is used." + * ^definition = "For each Boolean clock capability reported a `property` element is used." * type from ASN1ClockBits (required) * ^short = "Tells what the clock capability item is" * ^definition = "One of the capabilities of the clock as reportedD." diff --git a/input/fsh/ValueSet.ASN1ClockBits.fsh b/input/fsh/ValueSet.ASN1ClockBits.fsh index 15642ad..21fc01c 100644 --- a/input/fsh/ValueSet.ASN1ClockBits.fsh +++ b/input/fsh/ValueSet.ASN1ClockBits.fsh @@ -3,7 +3,7 @@ Id: ASN1ClockBits Title: "ANS1ToHL7 codes defined for Boolean Clock attributes" Description: "ValueSet for the ANS1ToHL7 codes that are not derived from enumeration measurements." * ^meta.profile = "http://hl7.org/fhir/StructureDefinition/shareablevalueset" -* ^url = "http://hl7.org/fhir/uv/phd/ValueSet/ASN1ClockBits" +* ^url = "http://terminology.hl7.org/ValueSet/ASN1ClockBits" * ^version = "current" // * ^status = #draft * ^experimental = false diff --git a/input/ignoreWarnings.txt b/input/ignoreWarnings.txt index 6959c83..90df0c3 100644 --- a/input/ignoreWarnings.txt +++ b/input/ignoreWarnings.txt @@ -18,8 +18,8 @@ This element does not match any known slice defined in the profile http://hl7.or This element does not match any known slice defined in the profile http://hl7.org/fhir/StructureDefinition/bodytemp|4.0.1 (this may not be a problem, but you should check that it's not intended to match a slice) # When a Phd compound observation is also a vital sign this warning is generated, but this is not a real problem. -This element does not match any known slice Defined in the profile http://hl7.org/fhir/uv/phd/StructureDefinition/PhdCompoundNumericObservation|2.1.0 (this may not be a problem, but you should check that it's not intended to match a slice) -This element does not match any known slice defined in the profile http://hl7.org/fhir/uv/phd/StructureDefinition/PhdCompoundObservation|2.1.0 (this may not be a problem, but you should check that it's not intended to match a slice) +This element does not match any known slice Defined in the profile http://hl7.org/fhir/uv/phd/StructureDefinition/PhdCompoundNumericObservation|2.0.0-ballot2 (this may not be a problem, but you should check that it's not intended to match a slice) +This element does not match any known slice defined in the profile http://hl7.org/fhir/uv/phd/StructureDefinition/PhdCompoundObservation|2.0.0-ballot2 (this may not be a problem, but you should check that it's not intended to match a slice) # This warning is generated when different categories are required in resources that comply with different profiles like vitals-signs and phd: None of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/uv/phd/CodeSystem/PhdObservationCategories#phd) @@ -28,7 +28,7 @@ None of the codings provided are in the value set 'Observation Category Codes' ( The type of property 'code' is 'code', but no ValueSet information was found, so the codes will be validated as internal codes # This is generated for all observations that use the vital signs category. This warning can be ignored safely. -This element does not match any known slice defined in the profile http://hl7.org/fhir/uv/phd/StructureDefinition/PhdNumericObservation|2.1.0 (this may not be a problem, but you should check that it's not intended to match a slice) +This element does not match any known slice defined in the profile http://hl7.org/fhir/uv/phd/StructureDefinition/PhdNumericObservation|2.0.0-ballot2 (this may not be a problem, but you should check that it's not intended to match a slice) # This informational message is out of our control. The extension http://hl7.org/fhir/StructureDefinition/elementdefinition-maxValueSet|5.2.0 is deprecated diff --git a/input/intro-notes/StructureDefinition-PhdBaseObservation-notes.md b/input/intro-notes/StructureDefinition-PhdBaseObservation-notes.md index 7e123e6..539d79d 100644 --- a/input/intro-notes/StructureDefinition-PhdBaseObservation-notes.md +++ b/input/intro-notes/StructureDefinition-PhdBaseObservation-notes.md @@ -29,7 +29,7 @@ An example of the this identifier from [this example](Observation-numeric-spotnu {% fragment Observation/numeric-spotnumeric JSON EXCEPT:identifier %} ### Obtaining the Type of observation -One obtains the IEEE 11073-10101 observation type for the `code` element in the same manner for all metric observations. See the section [MDC Nomenclature codes](Nomenclaturecodes.html) for the details. +One obtains the IEEE 11073-10101 observation type for the `code` element in the same manner for all types of observations. See the section [MDC Nomenclature codes](Nomenclaturecodes.html) for the details. ### Subject The `subject` element normally points to the PhdPatient resource using the logical id of the Patient resource, for example 'Patient/123546'. For device settings known to the PHG it should point to the PHD. @@ -76,7 +76,7 @@ For IEEE 11073-10206 timestamps the following table can be used: | Tick counter | Yes | n.a. | n.a. | Map to PHG timeline, including PHG offset | Yes | | Tick counter | No | n.a. | n.a. | Throw away | n.a. | -The PHG maps the 'converted' timestamp to either an `Observation.effectiveDateTime` element or an `Observation.effectivePeriod` element. The second situation occurs when the metric observation includes a Measurement-Duration (duration) attribute. Then the timestamp attribute gives the start of the period and the end of the period is obtained by adding the Measurement-Duration value to it. If no timestamp is provided, the PHG, using the time of reception of the observation as its timestamp must then do the reverse; the time of reception is the end time and the start time is given by subtracting the Measurement-Duration value from it. +The PHG maps the 'converted' timestamp to either an `Observation.effectiveDateTime` element or an `Observation.effectivePeriod` element. The second situation occurs when the observation includes a Measurement-Duration (duration) attribute. Then the timestamp attribute gives the start of the period and the end of the period is obtained by adding the Measurement-Duration value to it. If no timestamp is provided, the PHG, using the time of reception of the observation as its timestamp must then do the reverse; the time of reception is the end time and the start time is given by subtracting the Measurement-Duration value from it. When the PHG modifies an Observation's timestamp as received from the PHD it shall also generate a Coincident Timestamp observation that records how the `Observation.effective[x]` element is generated. ### extension: Coincident timestamp reference diff --git a/input/intro-notes/StructureDefinition-PhdCodedEnumerationObservation-intro.md b/input/intro-notes/StructureDefinition-PhdCodedEnumerationObservation-intro.md index 35544a3..8e691a4 100644 --- a/input/intro-notes/StructureDefinition-PhdCodedEnumerationObservation-intro.md +++ b/input/intro-notes/StructureDefinition-PhdCodedEnumerationObservation-intro.md @@ -1,4 +1,4 @@ -The Coded Enumeration Observation Profile is used when the PHD metric measurement is represented by one of a limited set of codes. This corresponds to the Single Event Observation class in IEEE 11073-10206 ACOM and the Simple Discrete Observation in GHS. +The Coded Enumeration Observation Profile is used when the PHD observation value is represented by one of a limited set of codes. This corresponds to the Single Event Observation class in IEEE 11073-10206 ACOM and the Simple Discrete Observation in GHS. The MDC code of the value in this observation resource corresponds to the value attribute in these ACOM and GHS observation classes. diff --git a/input/intro-notes/StructureDefinition-PhdCompoundNumericObservation-intro.md b/input/intro-notes/StructureDefinition-PhdCompoundNumericObservation-intro.md index 216abf4..aaaab1e 100644 --- a/input/intro-notes/StructureDefinition-PhdCompoundNumericObservation-intro.md +++ b/input/intro-notes/StructureDefinition-PhdCompoundNumericObservation-intro.md @@ -1,3 +1,3 @@ -The Compound Numeric Observation Profile can be used when the PHD metric measurement is a vector or a set of related numeric concepts. Examples would be the x, y, and z components of the acceleration, the systolic, diastolic, and mean components of a blood pressure measurement, or the set of package positions and associated questions in the Advanced Medication Monitor. +The Compound Numeric Observation Profile can be used when the PHD observation value is a vector or a set of related numeric concepts. Examples would be the x, y, and z components of the acceleration, the systolic, diastolic, and mean components of a blood pressure measurement, or the set of package positions and associated questions in the Advanced Medication Monitor. IEEE 11073-10206 ACOM supports more generic compounds where the components can be numeric, codeable concepts, sample arrays or strings. This profile is kept for backwards compatibility with older IEEE 11073-20601-based implementations. \ No newline at end of file diff --git a/input/intro-notes/StructureDefinition-PhdCompoundNumericObservation-notes.md b/input/intro-notes/StructureDefinition-PhdCompoundNumericObservation-notes.md index 64734cf..7127630 100644 --- a/input/intro-notes/StructureDefinition-PhdCompoundNumericObservation-notes.md +++ b/input/intro-notes/StructureDefinition-PhdCompoundNumericObservation-notes.md @@ -10,5 +10,5 @@ The structure definition is given [here](StructureDefinition-PhdCompoundNumericO ### Additional Numerical Measurement Information IEEE 11073-20601 numeric measurement values may have some additional optional attributes that are used only for numerics. An example of such a numeric-only additional attribute is one that describes the accuracy of the measurement value. -In FHIR these attributes are reported in extensions. The same extensions that are used as for [non-compoud numeric measurements](StructureDefinition-PhdNumericObservation.html) can be used for the numeric components. +In FHIR these attributes are reported in extensions. The same extensions that are used as for [non-compound numeric measurements](StructureDefinition-PhdNumericObservation.html) can be used for the numeric components. diff --git a/input/intro-notes/StructureDefinition-PhdCompoundObservation-intro.md b/input/intro-notes/StructureDefinition-PhdCompoundObservation-intro.md index 2911a28..15d2bd4 100644 --- a/input/intro-notes/StructureDefinition-PhdCompoundObservation-intro.md +++ b/input/intro-notes/StructureDefinition-PhdCompoundObservation-intro.md @@ -1,2 +1,2 @@ -The Compound Observation Profile is used when the PHD metric measurement is a vector or a set of related measured components that should be interpreted together. Examples would be the x, y, and z components of the acceleration, the systolic, diastolic, and mean components of a blood pressure measurement. These examples have only numeric components. An example with heterogeneous components would be a glucose measurement reporting the blood glucose level as a numeric and the meal context as a codeable concept. +The Compound Observation Profile is used when the PHD observation value is a vector or a set of related measured components that should be interpreted together. Examples would be the x, y, and z components of the acceleration, the systolic, diastolic, and mean components of a blood pressure measurement. These examples have only numeric components. An example with heterogeneous components would be a glucose measurement reporting the blood glucose level as a numeric and the meal context as a codeable concept. diff --git a/input/intro-notes/StructureDefinition-PhdCompoundObservation-notes.md b/input/intro-notes/StructureDefinition-PhdCompoundObservation-notes.md index c1a91e6..1f011df 100644 --- a/input/intro-notes/StructureDefinition-PhdCompoundObservation-notes.md +++ b/input/intro-notes/StructureDefinition-PhdCompoundObservation-notes.md @@ -1,4 +1,4 @@ -The Phd Compound Observation Profile can be used when the PHD metric measurement is a vector or a set of related numeric concepts. Examples would be the x, y, and z components of the acceleration, the systolic, diastolic, and mean components of a blood pressure measurement, or the set of package positions and associated questions in the Advanced Medication Monitor. +The Phd Compound Observation Profile can be used when the PHD observation value is a vector or a set of related numeric concepts. Examples would be the x, y, and z components of the acceleration, the systolic, diastolic, and mean components of a blood pressure measurement, or the set of package positions and associated questions in the Advanced Medication Monitor. The IEEE 11073-10206 model supports more generic compounds where the components can be numeric, codeable concepts, sample arrays or strings. Each individual entry of the compound value is reported in an `Observation.component` element. diff --git a/input/pagecontent/DIMtoFHIRMapping.md b/input/pagecontent/DIMtoFHIRMapping.md index 9fc1902..9fa8e89 100644 --- a/input/pagecontent/DIMtoFHIRMapping.md +++ b/input/pagecontent/DIMtoFHIRMapping.md @@ -42,9 +42,9 @@ border: 1px solid black; border-collapse:collapse; padding: 6px;}</style> -### Scalar Numeric Metric Object Mapping Example +### Numeric Observation Mapping Example -The simplest example of a mapping of a Numeric Metric object to a FHIR Observation resource is as follows +The simplest example of a mapping of an ACOM Numeric Observation to a FHIR Observation resource is as follows |ACOM Numeric Observation Attribute|Meaning|FHIR Observation element| |-|---|---| @@ -53,9 +53,9 @@ The simplest example of a mapping of a Numeric Metric object to a FHIR Observati |Value|Gives the value of the measurement|`valueQuantity.value`| |Unit-Code|Gives the units of the measurement as an IEEE 11073-10101 code. Shall be translated to the equivalent UCUM code and system when available.|`valueQuantity.code`| -This mapping applies to several simple types of PHD measurements that are scalars, for example body temperature, body mass, body height, glucose concentration, among many others. This Implementation Guide specifies a structure definition profile that applies to all scalar Numeric Metric measurements. +This mapping applies to several simple types of PHD measurements that are scalars, for example body temperature, body mass, body height, glucose concentration, among many others. This Implementation Guide specifies a structure definition profile that applies to all scalar Numeric observations. -Scalar numeric measurements are the most common type of PHD measurement. +Numerical observations are the most common type of PHD measurement. ### Compound (Numeric) Observation Mapping Example diff --git a/input/pagecontent/Glossary.md b/input/pagecontent/Glossary.md index 27f2519..682a2ef 100644 --- a/input/pagecontent/Glossary.md +++ b/input/pagecontent/Glossary.md @@ -15,6 +15,7 @@ This glossary lists abbreviations and acronyms used throughout this Implementati | IG | Implementation Guide | | LOINC | Logical Observation Identifiers Names and Codes | | MDC | Medical Device Communication (nomenclature codes, IEEE 11073-10101) | +| MDS | Medical Device System (from IEEE 11073-20601) | | MRN | Medical Record Number | | PCHA | Personal Connected Health Alliance | | PHD | Personal Health Device | diff --git a/input/pagecontent/ProfilesOverview.md b/input/pagecontent/ProfilesOverview.md index 5f92ea3..95a1bcd 100644 --- a/input/pagecontent/ProfilesOverview.md +++ b/input/pagecontent/ProfilesOverview.md @@ -40,7 +40,7 @@ Further information on the mapping of the ACOM Observation types to FHIR Observa <figcaption><i>IEEE 11073-10206 ACOM Observation classes</i></figcaption> </figure> -The value-type of the measurement is the main difference between the observation-related profiles. The remaining attributes in the metric objects are common to all measurements and are thus mapped in the same way to FHIR. +The value-type of the measurement is the main difference between the observation-related profiles. The other attributes in the Observation objects are common to all types of Observations and are thus mapped in the same way to FHIR. ### PHD Device Profile The PHD Device profile for the IEEE 11073-10206 ACOM System Information object supports the static device information like manufacturer name, model number, serial number, time properties, device type (blood pressure cuff, pulse oximeter, etc.), system identifier, transport address, etc. There is also a udiCarrier element that supports the UDI attribute. diff --git a/publication-request.json b/publication-request.json index 3438405..909a288 100644 --- a/publication-request.json +++ b/publication-request.json @@ -1,7 +1,7 @@ { "package-id" : "hl7.fhir.uv.phd", - "version" : "2.1.0", - "path" : "http://hl7.org/fhir/uv/phd/2.1.0", + "version" : "2.0.0-ballot2", + "path" : "http://hl7.org/fhir/uv/phd/2025Sep", "mode" : "working", "status": "ballot", "sequence": "STU 2",