Stream: implementers
Topic: Medication*Statement
Philipp Daumke (Nov 15 2018 at 07:23):
Hi all,
a Newbie question: For the statement "Aspirin 500mg Tbl. 1-0-0", do I need a Medication and a MedicationStatement? Everything seems to be in the MedicationStatement except for the form ('tablet') which is an attribute of Medication.
Thanks for your help
Philipp
Grahame Grieve (Nov 15 2018 at 07:25):
it depends on your code - most codes for medications are specific about the form
Grahame Grieve (Nov 15 2018 at 07:26):
if the code system is not... then you'll need a medication
Grahame Grieve (Nov 15 2018 at 07:26):
but RxNorm, etc, usually are
Philipp Daumke (Nov 15 2018 at 07:32):
OK, thanks a lot.
Philipp Daumke (Nov 15 2018 at 07:54):
Although I would argue that the implementation shouldn't be dependent from the terminology binding. Otherwie, there's another interoperability problem.
Lloyd McKenzie (Nov 15 2018 at 08:00):
That's pretty much impossible. Form code, strength, ingredients, etc. are all impacted by choice of terminology. If you're sending something where those characteristics are implicit in the code, it's almost impossible to get implementers to want to send them redundantly elsewhere - first because it's more work and second because it provides opportunity for inconsistency/error. And standardization of terminologies on an international basis is not in the cards because the terminologies are so tightly tied to regulation and regulation is tightly tied to jurisdiction.
Lloyd McKenzie (Nov 15 2018 at 08:01):
In the absense of shared codes, interoperability will happen through CodeableConcept.text and narrative. Both of those are relatively accomodating of differences in which elements are populated.
Grahame Grieve (Nov 15 2018 at 08:57):
the implementation shouldn't be dependent from the terminology binding.
I absolutely agree, but that's not the world we live in
Simone Heckmann (Nov 15 2018 at 13:25):
I think it's a localization issue. It depends on the CodeSystem used in a specific realm. Any implementation that supports different jurisdictions may have to adapt to the local situation.
On a side note: I believe the version where you always reference a Medication resource should work in any situation...
Your catalogue of Medication resources could be loaded into your server at configuration time and you could then at runtime search for them by code to get the references.
....or even do it in one step by bundeling MedicationStatement ans Medication into a transaction and use a conditional create by code on the Medication entry... The server would then update the temporary uuid of the entry reference with the actual reference that matches the Medication resource...
Last updated: Apr 12 2022 at 19:14 UTC
