Stream: Medicolegal Death Investigation
Topic: Tracking Number Extensions
Kellie Broxton (Jan 05 2022 at 18:50):
The Extension-tracking-number has a valueIdentifier code for Birth Certificate (BCT) with a value of 15075 in the bundle-mdi-to-edrs-j-rogers example. After examining the IG I was expecting a TrackingNumberType for the mdi-case-number and/or edrs-file-number. Will these not be sent? If not, is the 15075 equivalent to our edrs file number and if so, does this mean the examples are updates to an existing case within the edrs system as opposed to a new case?
David deRoode (Jan 05 2022 at 21:08):
Note that the extension tracking number cardinality is 0..*, so multiple identifiers are allowed to be sent, but currently there are not constraints/rules for what that tracking value is, where it comes from, when or who creates it, etc. Regarding your overarching question/point: what is an appropriate, meaningful tracking number here is key. Titles matter for extensions, but also descriptions and notes to make the intended appropriate use will be key.
The example containing '15075' in J Rogers example is likely from some other birth/death examples that were used as a starting point. But, any use of a birth certificate identifier is for this IG/scenario...definitely confusing and will be updated to a more appropriate/meaningful tracking identifier based on clarifications once we get clarity on how this tracking identifiers relates to other possible identifiers.
Myung Choi (Jan 11 2022 at 13:14):
@Diana Wright The MDI case number in the test case should match mdi-case-number in https://build.fhir.org/ig/HL7/fhir-mdi-ig/ValueSet-ValueSet-tracking-number-type.html#logical-definition-cld. Right?
I think we can also add edrs-file-number to use for our update api testing.
Myung Choi (Jan 11 2022 at 13:16):
David deRoode said:
Note that the extension tracking number cardinality is 0..*, so multiple identifiers are allowed to be sent, but currently there are not constraints/rules for what that tracking value is, where it comes from, when or who creates it, etc. Regarding your overarching question/point: what is an appropriate, meaningful tracking number here is key. Titles matter for extensions, but also descriptions and notes to make the intended appropriate use will be key.
The example containing '15075' in J Rogers example is likely from some other birth/death examples that were used as a starting point. But, any use of a birth certificate identifier is for this IG/scenario...definitely confusing and will be updated to a more appropriate/meaningful tracking identifier based on clarifications once we get clarity on how this tracking identifiers relates to other possible identifiers.
Even if the cardinality is 0..*, the IG does indicate the binding for the valueIdentifier to valueSet, http://hl7.org/fhir/us/mdi/ValueSet/ValueSet-tracking-number-type. So Yes, I think having an example that shows this binding would be very helpful. And the the valueSet system has three options to choose (refer to https://build.fhir.org/ig/HL7/fhir-mdi-ig/ValueSet-ValueSet-tracking-number-type.html#expansion).
And, it wouldn't be a bad idea to restrict the values to this binding.
Last updated: Apr 12 2022 at 19:14 UTC
