FHIR Chat · MedicationKnowledge · Medication

Stream: Medication

Topic: MedicationKnowledge


view this post on Zulip Patricia Almeyda Polanco (Feb 12 2020 at 21:00):

We have 2 medication of the same supplements in differents formats, bottle and pill, that can be mapped in these 4 resources

medication.yaml medicationKnowlwdge.yaml medicationKnowlwdge-pill.yaml medication-pill.yaml

As you can see both medication resources are almost equal and contain the same information that we have in medicationKnowledge, the only changes is the identifiers. We are considering removing medication resources and only use medicationKnowledge. this makes sense? In this case, how we can link medication request to medicationKnowledge?

view this post on Zulip Jean Duteau (Feb 12 2020 at 21:02):

you can't. MedicationRequests link to Medication resources or to the medication CodeableConcept because the intent is just to provide enough information to identify the specific medication requested.

view this post on Zulip Patricia Almeyda Polanco (Feb 12 2020 at 21:11):

We can use CodeableConcept to link with medicationKnowledges

view this post on Zulip Jean Duteau (Feb 12 2020 at 21:21):

Yes. the request would have the code and then someone could look up the MedicationKnowledge via the code. That is an indirect linking.

view this post on Zulip Patricia Almeyda Polanco (Feb 12 2020 at 21:23):

thanks

view this post on Zulip Patricia Almeyda Polanco (Feb 12 2020 at 21:28):

so, to be clear: we wouldn’t have any resource of type Medication, only MedicationKnowlege link to MedicationRequest via CodeableConcept

view this post on Zulip Jean Duteau (Feb 12 2020 at 21:30):

I agree that the MedRequest would only have the medicationCodeableConcept. That is the "normal" way of specifying the code in the request. You only need the Medication resource if you are specifying compounds or if you need to provide more information than the code provides (some codes have multiple quantities, maybe you want to specify a specific lot/batch number, etc.)


Last updated: Apr 12 2022 at 19:14 UTC