Loading...

XML

Word

Printable

JSON

Specification:

Medicolegal Death Investigation (MDI) (FHIR)
Raised in Version:

current
Work Group:

Public Health
Related Artifact(s):

Observation - Cause of Death Part 1 [deprecated]
Related Page(s):

Security Recommendations [deprecated]
Resolution Description:
Hide

We will fix the interval component to correctly display value[x] options on all 3 tabs (Differential, Key Elements, and Snapshot)

We will add a 2nd example file for Cause of Death Part 1, using valueQuantity

We will improve the Observation.component:interval.value[x] description to inform and guide users that the Quantity is only to be used for an amount of time
Show
We will fix the interval component to correctly display value [x] options on all 3 tabs (Differential, Key Elements, and Snapshot) We will add a 2nd example file for Cause of Death Part 1, using valueQuantity We will improve the Observation.component:interval.value [x] description to inform and guide users that the Quantity is only to be used for an amount of time
Resolution Vote:
Sarah Gaunt / Craig Newman : 28-0-0
Change Category:
Clarification
Change Impact:
Non-substantive

I see that valueQuantity for the “interval” component is listed as a possible option on the Differential Table tab of the Cause of Death Part 1 Observation page, but I don’t see it on the Key Elements Table or Snapshot Table tabs. Is this just a graphical issue, or is there a specific reason why it would be shown only on the Differential Table?
Would it make sense to include a ValueSet for the units for the valueQuantity to only include time measurements? The VRDR FHIR IG has a ValueSet for Units of Age (http://hl7.org/fhir/us/vrdr/ValueSet-vrdr-units-of-age-vs.html) and I’m wondering if something similar could be used on the MDI IG, either with this exact ValueSet or a new MDI-specific one. This could help inform and guide users that the Quantity is only to be used for an amount of time and not any other type of measurement. Is this even a constraint that we are able to make that would be in alignment with the FHIR specification since this component now has two possible value types for the interval component, string and Quantity?

(Based on email from Netsmart: Reece Berens <rberens@ntst.com> )