FHIR Chat · MedicationKnowledge · implementers

Stream: implementers

Topic: MedicationKnowledge


view this post on Zulip Melva Peters (Apr 16 2018 at 21:19):

The Pharmacy Work Group is currently investigating the requirements for a MedicationKnowledge or "drug information" type resource. A draft resource has been added to the current build. We are seeking input from implementers on the resource - both what has been proposed in the first draft as well as other requirements. http://build.fhir.org/medicationknowledge.html

view this post on Zulip Jose Costa Teixeira (Apr 16 2018 at 21:19):

How should that input be? Gforge items or on the mailing list?

view this post on Zulip Melva Peters (Apr 16 2018 at 21:28):

You can add your comments in to Gforge

view this post on Zulip Jose Costa Teixeira (Apr 18 2018 at 06:24):

I checked the resource but I don't understand its scope. Perhaps best to discuss at Cologne what is the problem this is tyring to solve or what are the use cases.

view this post on Zulip Jose Costa Teixeira (Apr 18 2018 at 06:25):

We have a need to consult/exchange and cross-check product definition information; FHIR is the perfect way to do that, but i don't see what requirements are met with this resource.

view this post on Zulip Igor Sirkovich (Apr 18 2018 at 15:02):

I'm wondering if management of drug formularies is in scope of this resource, e.g. a List or Catalog of MedicationKnowledge resources.

view this post on Zulip Jose Costa Teixeira (Apr 18 2018 at 15:04):

that is the need i was pointing to, but this resource seems only partially targeted at the use cases I have there.

view this post on Zulip Jose Costa Teixeira (Apr 18 2018 at 15:08):

formularies can cover officinal preparations, but this one doesn't seem to go there. formularies also explain cost breakdowns, the use of "code" seems closer to what you'd say in a prescription than what you'd use in a formulary...

view this post on Zulip Jose Costa Teixeira (Apr 18 2018 at 15:09):

so i think I have a different use case in mind, given the gaps.

view this post on Zulip Jose Costa Teixeira (Apr 18 2018 at 15:13):

my use case is :
I need to query medicine definitions - in a ad-hoc query or i get them as a catalog, from a vendor. The definitions (the type and value of the attributes) can be locally defined or regulated, and i need te enrich that definition and serve it forward. I need to relate drugs to other drugs (and also to conditions and to "contexts"). "medicine" can be a regulated drug, a local formula my hospital defined last year, or something i just made up.

view this post on Zulip Jose Costa Teixeira (Apr 18 2018 at 15:14):

sorry for the informal use case description :-)

view this post on Zulip Melva Peters (Apr 18 2018 at 15:19):

@Igor Sirkovich That is definitely one of the use cases that we are trying to meet. In addition, we have implementers who are implementing drug terminologies that are providing requirements.

view this post on Zulip Jose Costa Teixeira (Nov 10 2020 at 16:33):

Hi. A couple of questions - not sure they were already considered:

  1. MedicationKnowledge.ingredient.isActive - I understood this was going to change to .roleas a CodeableConcept?
  2. MedicationKnowledge.relatedMedicationKnowledge.type - is this the type of the related medication? Or it is the type of the relation? I'm looking for relations of different types, like "can be used in", "is specialization of", or "is usually given with"

view this post on Zulip Jose Costa Teixeira (Nov 10 2020 at 16:49):

@Jean Duteau @Melva Peters ?

view this post on Zulip Jean Duteau (Nov 10 2020 at 16:52):

1) We are looking at switching to using the Ingredient resource/type. Until that resolves, we aren't considering making any changes at this time.
2) We are working through all of our vocabulary bindings to provide example value sets, but we need to use UTG or get a ruling that we don't have to use UTG, so it is taking awhile.

view this post on Zulip Jose Costa Teixeira (Nov 10 2020 at 17:03):

Ok on 1 (not using the resource/type, but understand no decision until then). This is such an old discussion that I was afraid we'd changed and changed back already.

view this post on Zulip Jose Costa Teixeira (Nov 10 2020 at 17:06):

  1. I don't mean the terminology, this is a CodeableConcept and that is fine.
    I meant the description of the field: This being a Key-value pair, I'd expect the relatedMedKnowledge.type to be about the type of relation, but the description says "The category of the associated MedicationKnowledge reference".

view this post on Zulip Jean Duteau (Nov 10 2020 at 17:07):

That is correct. And when we have the example value set, you'll see what types of values we intended with this.

view this post on Zulip Jose Costa Teixeira (Nov 10 2020 at 17:30):

Then for the type of relationship do I need an extension?

view this post on Zulip Jose Costa Teixeira (Nov 10 2020 at 17:32):

(the category of the type of medication knowledge is actually already in the target medicationknowledge, I don't see what this attribute in the relationship could be. An example would help)

view this post on Zulip Jose Costa Teixeira (Nov 11 2020 at 17:44):

@Jean Duteau do I expect to need an extension for the type of relation? Better, do you recall one example value (I don't need the value set)


Last updated: Apr 12 2022 at 19:14 UTC