Stream: implementers
Topic: Medication Statement - DSTU2
Bhanu Vemuri (Oct 29 2018 at 19:40):
I am from payer organization and we are planning to develop a solution to send patient medication history to hospital EHR system using FHIR DSTU2. We are in the process of development and realize that we got data only for Medication description , Dosage and not the medication codes( like NDC or RxNorm).
Are we able to build complaint solution without codes? As part of validation FHIR Specification will confirm to just medication description without a code? I see "MedicationStatment.Medication" as codeable concept and it's 1..1
Can someone please provide a recommendation on what to do since we do not want to build something that is non complaint?
https://www.hl7.org/fhir/DSTU2/medicationstatement-definitions.html
Michele Mottini (Oct 29 2018 at 19:45):
You can use a CodeableConcept with only its text element populated with the medication description - that is perfectly legal
Michele Mottini (Oct 29 2018 at 19:46):
Having said that, not having a medication code would limit what the receiving system could do with that information
Scott Robertson (Oct 29 2018 at 20:28):
I'm surprised that as a payer you do not have a specific product code. Typically, payment is based on the specific product.
As @Michele Mottini pointed out, while you can send just the text name that will be of minimal use for the EHR. Aside from displaying the text to the user, without a code the EHR would have difficulty performing medication reconciliation/adherence reporting and probably would not be able to use the information for interaction checking.
Bhanu Vemuri (Oct 29 2018 at 20:57):
Thank you for the quick reply. We do have codes but not in the tables from which we can consume quickly without additional ETL work. So, trying to understand, can we start with text and enhance it later to include codes if FHIR response can confirm to be complaint during validation.
Brian Postlethwaite (Oct 30 2018 at 08:26):
You can also put your codes in there too. Then if mappings are created, they can be applied later too.
Or could create mappings other side for the most common ones, better than nothing.
Scott Robertson (Oct 30 2018 at 16:20):
@Bhanu Vemuri Your step-wise approach (text now, add codes later) should work (should be compliant)
Last updated: Apr 12 2022 at 19:14 UTC
