Stream: argonaut
Topic: adding a must support for derivedFrom to US-Core
Eric Haas (Feb 08 2017 at 02:23):
RE US Meds IG. (STU3) We we discussing adding derivedFrom as a "must support" element for MedStatemnt, our discussion about getting the medications list hinges on orders being included in Medstatements and derived from the status = active and intent = order MedRequests. So we are considering whether should be in US-Core vs USMeds IG. Thoughts?
Eric Haas (Feb 08 2017 at 02:23):
"must support" is a 0..1 but "send it if you have it"
Eric Haas (Feb 08 2017 at 02:24):
Main reason is if a user wants to know more about the dosing they can go an fetch yon MedRequest
Eric Haas (Feb 20 2017 at 18:23):
More on this element. Pharmacy has discussed very recently constraining the type in US-Core from its current definition of *resource(Any)* (can't find active tracker). And the list below aligns pretty much with what they are thinking. Unfortunately they were unable resolve prior to STU3 deadline. However, I think we should go ahead and constrain the type in US-Core from *resource(Any)* to reference only:
- MedicationRequest
- MedicationDispense
- Claim
- Observation
- QuestionnaireResponse
(What about Compositions or Binaries or DocumentReference for other sources?)
Lloyd McKenzie (Feb 20 2017 at 23:18):
Could be derived from a different MedicationStatement too. Or a CarePlan
Last updated: Apr 12 2022 at 19:14 UTC
