Stream: Vital Records Birth & Fetal Death
Topic: IG Fixes
Sarah Gaunt (Sep 01 2020 at 06:04):
- changed all profiles in the medical health information section on the BC to have Patient-Mother as the subject and removed focus
- updated examples to match above
- updated the Plurality example that had the wrong mother
- regenerated live birth bundles with double mother
- updated all bundles to contain meta.profile and fixed examples
Eric Trinh (Genesis) (Sep 08 2020 at 18:53):
Hello, we run into a strange error in the validator tool. It reports Snomed code 434691000124101 and 434621000124103 not found even though they are included in the value set on PHINVADS (https://phinvads.cdc.gov/vads/ViewValueSet.action?id=02D906AD-19E7-4D85-95BB-6D71F9DBDC44)
AJ Johnson (Sep 08 2020 at 21:10):
I'm also running into some validator errors that I'm not sure how to deal with; specifically, it looks like several of the newly defined BFDR profiles have definitions that aren't live/valid links yet, so I think the errors that I'm getting are related to that. Here's an example:
Error @ Bundle.entry[0].resource.ofType(Composition).subject (line 36, col56) : Unable to find matching profile for Patient/2019++05806 among choices: http://hl7.org/fhir/us/fhir-vr-common-ig/StructureDefinition/Patient-child
Are these errors safe to ignore? Will those links be added in time? Are the links to the profile definition incorrect? Thanks!
AJ Johnson (Sep 09 2020 at 14:47):
^Feel free to disregard this message. It seems like these errors were by-products of other problems. They just disappeared while correcting other errors in the document.
Cindy Bush (Sep 09 2020 at 20:13):
Thanks for the updates, Eric and AJ! @Sarah Gaunt Not sure if you saw these issues yet. Thanks!
AJ Johnson (Sep 11 2020 at 16:58):
@Sarah Gaunt @Cindy Bush I was just running some tests to consume documents and I believe I found a small error in the example document. In the live birth jurisdiction bundle (and possibly others), the Organization's identifier system is: "http://hl7.org.fhir/sid/us-npi", which I am guessing should be identical to the Practitioner's identifier system: "http://hl7.org/fhir/sid/us-npi" (note one is "org/fhir", one is "org.fhir"). I adjusted my code to work around it, but just wanted to get that cleared up - thanks!
Sarah Gaunt (Sep 11 2020 at 17:04):
Thanks @AJ Johnson - you're correct - they should both be: http://hl7.org/fhir/sid/us-npi (from https://www.hl7.org/fhir/identifier-registry.html)
Sarah Gaunt (Sep 11 2020 at 17:55):
@AJ Johnson re your email around the one error: Error @ Bundle.entry[0].resource.ofType(Composition).section[0].entry[3] (line 81, col30) : Profile http://hl7.org/fhir/us/bfdr/StructureDefinition/Composition-jurisdiction-live-birth-report, Element matches more than one slice - APGARScore, plurality. We've had a few similar issues with the composition.section.entry slicing and the validator being unable to differentiate between the slices. I'll look into this one - I'm pretty sure it will be an issue on my end and not on your end, but will let you know what I find.
AJ Johnson (Sep 11 2020 at 18:24):
Thanks @Sarah Gaunt for the update!
AJ Johnson (Sep 14 2020 at 14:20):
Forgot to put this update here on Friday, but that Error @ Bundle.entry[0].resource.ofType(Composition).section[0].entry[3] (line 81, col30) : Profile http://hl7.org/fhir/us/bfdr/StructureDefinition/Composition-jurisdiction-live-birth-report, Element matches more than one slice - APGARScore, pluralitywas caused by my accidentally setting the Reference to the father's paternity acknowledgment signed to be the same url as the plurality observation. Thanks @Eric Trinh (Genesis) for finding that error!
Last updated: Apr 12 2022 at 19:14 UTC
