Stream: argonaut
Topic: US-Core
Travis Stenerson (May 23 2017 at 21:50):
Hi guys, I imagine Argonaut is going to continue to use the US-Core profiles? If that's the case, does anyone have insight into why MedicationRequest is among them, but ProcedureRequest is not? Will Argonaut participants be able to handle ProcedureRequests returned as a decision from a system using CDS-Hooks?
Eric Haas (May 23 2017 at 22:23):
Why.. because was not a Common Clinical Data Set ( CCDS ) Data Element and that was the initial scope.
Jeffrey Danford (Jun 19 2017 at 20:20):
I'm looking at the US Core profile for Immunizations and I'm trying to understand Immunization.status. The supported values are completed and entered-in-error, where DSTU2 additionally supported on-hold and in-progress. How are multi-part (i.e. more than one dose) immunizations represented? Are they always complete and the fact the immunization is in progress inferred from the number of doses in the series, or is nothing reported until the entire immunization is complete?
Jenni Syed (Jun 19 2017 at 21:26):
@Jeffrey Danford STU 3 Immunizations actually removed those statuses, which is the version US Core is based on: http://hl7.org/fhir/stu3/immunization.html
The profile itself didn't restrict the base value set at all.
Jenni Syed (Jun 19 2017 at 21:30):
We had restricted it in the Argonaut version that was against DSTU 2, with knowledge that the change was coming. GF#9070 has more detail/background
Jenni Syed (Jun 19 2017 at 21:34):
I don't think the Immunization.status was intended to indicate the status of a series, it just inherited the Med Admin status.
Jeffrey Danford (Jun 19 2017 at 21:35):
So how should the first of three doses be reported, if only one dose has been administered and the other two are scheduled for future dates?
Jenni Syed (Jun 19 2017 at 21:37):
Based on the documentation on the core resource, the status is for that specific dose. This may be a conversation that needs to migrate over to the normal implementers channel and PHER, since this is a question for the core resource
Jenni Syed (Jun 19 2017 at 21:38):
It does seem weird since they do have the list of doses in a series at the bottom, so you could put more than one dose in a single immunization event
Jenni Syed (Jun 19 2017 at 21:40):
I will say that our server doesn't fill out the protocol section yet.
Jenni Syed (Jun 19 2017 at 22:44):
Also, if you did want to accurately represent a half-done series, you wouldn't be able to do it with the status was there - there's no way to know which vaccines you list in that protocol section were done and which weren't
Jenni Syed (Jun 19 2017 at 22:44):
If you just listed the ones that were complete (likely what our server would do), then the status would be completed. However, I still think it's confusing to have the whole protocol list in a single event
Eric Haas (Jul 19 2017 at 17:41):
I have applied several technical edits baseded upon GForge trackers for US-Core (Filter for US Core in the 'Specification' field) and will be bringing these changed up for a committee vote in the near future.
There are, however, 2 more substantive changes that need further consideration and we don't have to make them as part of a new version if we focus only on a "technical update" but I'd like to consider them anyway....
GF#13180 : US_Core Medication constraint 1..1 .code dose not allow for compounded meds
GF#13127 : For MedicationStatement Profile consider whether the encounter should be must-support
@Michelle (Moseman) Miller, @Danielle Friend ?
Last updated: Apr 12 2022 at 19:14 UTC
