FHIR Chat · Produced From / Ingredient · BRR - Pharmacy model

Stream: BRR - Pharmacy model

Topic: Produced From / Ingredient


view this post on Zulip Jose Costa Teixeira (Nov 03 2020 at 06:55):

What is the difference between AdministrableProductDefinition.producedFrom and MedicinalProductDefinition.ingredient?

view this post on Zulip Jean Duteau (Nov 03 2020 at 07:08):

One describes the ingredients of the product, i.e. the actual substances that make up the product. The other describes multiple products that are combined to make the administrable product. For example, 5ml Dopamine 40mg/ml Concentrate for Solution for Infusion + 500ml 0.9% Sodium Chloride Solution. Each of the producedFrom products will have their own ingredients.

view this post on Zulip Jean Duteau (Nov 03 2020 at 07:09):

NOTE: The definition of AdministrableProduct does a fairly decent job explaining this: A medicinal product may consist of several items, which need to be combined before administration to the patient. The administrable (or "pharmaceutical") product - which differs in that it is now "mixed" from its components (if necessary) and is ready for use - is covered by this resource. The components themselves are ManufacturedItemDefinitions.

view this post on Zulip Jose Costa Teixeira (Nov 03 2020 at 07:20):

Ok thanks. Is that the difference between what is manufactured by the manufacturer and what is prepared after that?

view this post on Zulip Jose Costa Teixeira (Nov 03 2020 at 07:22):

In other words, how would this work for an officinal preparation? I presume the officinal preparation will also define a product that is made by hand in a pharmacy - is there a difference between those 2 concepts? or in the case of officinal preparation the difference fades away?

view this post on Zulip Jean Duteau (Nov 03 2020 at 07:23):

i don't think so. i've been told that products that are packaged like that (with multiple components that need to be mixed) are done due to potency concerns. I'm assuming that if they came pre-mixed, the potency would "fade away" as it sat on a shelf.

view this post on Zulip Jean Duteau (Nov 03 2020 at 07:24):

this isn't defining a product that is necessarily made by hand in a pharmacy. it could very well be something that the patient mixes at home.

view this post on Zulip Jean Duteau (Nov 03 2020 at 07:24):

i.e. it comes marketed as multiple separate product components in one package

view this post on Zulip Jose Costa Teixeira (Nov 03 2020 at 07:25):

I don't mean to ask whether those preparations would come in mixed or not. I mean to ask if I want to define an officinal preparation, what was "ProducedFrom" is now an "ingredient", right?

view this post on Zulip Jean Duteau (Nov 03 2020 at 07:25):

no.

view this post on Zulip Jose Costa Teixeira (Nov 03 2020 at 07:26):

an officinal preparation has already been mixed. The patient / nurse just needs to add water and apply.

view this post on Zulip Jose Costa Teixeira (Nov 03 2020 at 07:28):

I understand the difference between e.g. contraceptives and antibiotic cocktails that come in one box but are different tablets with different substances altogether (those just happen to be in a same box but are not ingredients, I expect).

view this post on Zulip Jose Costa Teixeira (Nov 03 2020 at 07:31):

I guess my question is : If I have one single resource type that describes a medicinal product (manufactured, pharmaceutical, officinal,...) do I need ProducedFrom and Ingredient as separate attributes?
If so, would that be the difference between "this was made from 2 different things and is now one single thing" vs "this is given to you as 2 different things, for you to make into 1 thing" ? Or another difference?

view this post on Zulip Jean Duteau (Nov 03 2020 at 07:35):

yes you do. If that Medicinal Product comes packaged as two separate products that are mixed together, you need to describe the following things:
a) the packaged product contains two separate products
b) each of those component products needs to be described: what are each product's ingredients, form, characteristics
c) you need to describe the characteristics of the final combined product that has been mixed: form, route, etc.

To properly define the product, you need to define the packaging characteristics of the product as well as the pharmaceutical characteristics of the product.

view this post on Zulip Jean Duteau (Nov 03 2020 at 07:35):

your problem is that you say "things" for both substances and products when they aren't the same.

view this post on Zulip Jean Duteau (Nov 03 2020 at 07:36):

to restate your sentences: "this was made from 2 different substances and is now one single product" vs "this is given to you as two different products, for you to make into 1 product"

view this post on Zulip Jean Duteau (Nov 03 2020 at 07:57):

I've found a product - Xyntha - that comes in two different kits:
a) 4-ml diluent volume, prefilled syringe, needleless transfer system, vial adapter, and a vial of Antihemophilic factor
b) 4-ml diluent volume, prefilled syringe, with the Antihemophilic factor also in the syringe but kept separate until you use the plunger to mix them.

They have different AdministrableProductDefinitions:
a) only 1 Part: 4ml syringe: Ingredients: Moroctocog Alfa 2000iU in 4mL; Sodium Chloride 0.036ml in 4ml; Sucrose; Histidine; Calcium Chloride; Polysorbate 80; Water 4mL in 4mL

b) 2 parts: 1 4mL single-use vial: Ingredients: Moroctocog Alfa 2000iU in 4mL; Sodium Chloride; Sucrose; Histidine; Calcium Chloride; Polysorbate 80. 1 4mL syringe: Ingredients: Sodium Chloride 0.036mg in 4mL; Water 4mL in 4mL

Both of these kits come with a bunch of other stuff that would also be described in the PackagedProductDefinition (alcohol swabs and some devices like butterfly needles) but are not described in the AdministrableProductDefinition.

view this post on Zulip Jose Costa Teixeira (Nov 03 2020 at 08:16):

Jean Duteau said:

your problem is that you say "things" for both substances and products when they aren't the same.

They are not the same, but my starting point is that they can be expressed from the same resource type (with different profiles).

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

(and it's not a problem, it is a hypothesis)

view this post on Zulip Jean Duteau (Nov 03 2020 at 08:18):

Jose Costa Teixeira said:

Jean Duteau said:

your problem is that you say "things" for both substances and products when they aren't the same.

They are not the same, but my starting point is that they can be expressed from the same resource type (with different profiles).

That will be interesting to see since one is using Substances and the other is using MedicinalProducts. Good luck! :)

view this post on Zulip Jose Costa Teixeira (Nov 03 2020 at 08:19):

same reasoning there.

view this post on Zulip Jose Costa Teixeira (Nov 03 2020 at 08:20):

a) the packaged product contains two separate products
b) each of those component products needs to be described: what are each product's ingredients, form, characteristics
c) you need to describe the characteristics of the final combined product that has been mixed: form, route, etc.

I understand here that we would have indeed 2 attributes:

  1. How this comes packaged (roughly speaking)
  2. How this is supposed to be used.

view this post on Zulip Jose Costa Teixeira (Nov 03 2020 at 08:26):

For the 1. packaging thing, is there a difference between
"this box contains active tablets and placebo tablets" and "this box contains 3 blisters totaling 84 tablets"? I guess that is relevant for regulators.

view this post on Zulip Rik Smithies (Nov 03 2020 at 11:39):

I guess that is relevant for regulators.

yes. And they are a key stakeholder. Plus anyone else who needs the full information. Those that don't need this can simply not use this level of detail. It is our job to make sure these work for people who want full detail, and those who want less detail (but still more than in the basic Medication resource). That is a key design constraint.

They are not the same, but my starting point is that they can be expressed from the same resource type (with different profiles). .. it is a hypothesis

Things that are commonly held to be distinct concepts in the domain, should not be modelled as the same resource type.

Domain concepts:

Medicinal product and substance (plenty of evidence that people treat these differently - the ISO Models, the existing XEVMPD EU wide implementation, that pre-dates ISO, the UK dm+d national drug catalogue)

Product and packs (plenty of evidence that people treat these differently, the ISO models, the existing XEVMPD EU wide implementation, UK dm+d, and others (the Irish one, the Australian one etc.))

Observations and procedures (plenty of evidence that people treat these differently, many EHRs implemented worldwide)

Of course, domains are wide and not everyone treats all these things as different. For very simple uses cases some of these may be the same (undifferentiated clinical notes in a consumer iPhone app for instance, or a UK system I worked on that had "entry" records that treated these as the same concept, but with a type code).

We need to differentiate these for the general case, to make life familiar for domain implementers.

view this post on Zulip Jose Costa Teixeira (Nov 03 2020 at 11:47):

I am just opening up a hypothesis of how we can meet the same requirements, let's keep the discussion open.

view this post on Zulip Jose Costa Teixeira (Nov 03 2020 at 11:48):

I understand that the content (in terms of "recipe" and the content (in terms of packaging) are separate concepts. I can handle that, regardless of whether a medicinal product and an administrable product are the same resource type or not.

view this post on Zulip Rik Smithies (Nov 03 2020 at 11:52):

At some point discussion has to reach a conclusion. Hypothesis are fine, but must be tested, with evidence. In FHIR that means seeing what people are actually doing in implementations.

view this post on Zulip Jose Costa Teixeira (Nov 03 2020 at 12:09):

I don't understand. I thought we had an agreement to develop a second hypothesis.

view this post on Zulip Jose Costa Teixeira (Nov 03 2020 at 12:09):

In FHIR that means working together.

view this post on Zulip Rik Smithies (Nov 03 2020 at 12:10):

I am not sure what you mean. There is nothing stopping you Jose. We are all working together, and the workgroup is the coordinating group.

view this post on Zulip Jose Costa Teixeira (Nov 03 2020 at 12:21):

I have the answer to my question, that allows me to continue working towards a different proposal.

view this post on Zulip Catherine Hosage Norman (Nov 03 2020 at 17:38):

PQ/CMC does not map to Medicinal Product this way. It there are two products in the package, there are two Medicinal products. They have completely different quality profiles. They get combined as an administrable product.

view this post on Zulip Rik Smithies (Nov 03 2020 at 18:08):

ManufacturedItemDefinition is the resource that is intended to represent the actual physical tablets, solutions etc, that get mixed. They are not normally considered to be a product in their own right, in the sense of something that is eventually marketed in a packaged form with licensed indications etc. They would have different quality profiles, of course.

view this post on Zulip Rik Smithies (Nov 03 2020 at 18:10):

The diagrams here illustrate this: http://build.fhir.org/medication-definition-module.html

view this post on Zulip Catherine Hosage Norman (Nov 03 2020 at 18:33):

I have see the diagram. That is not how we are mapping. If there are two products in the eCTD there will be two medicinal products.

view this post on Zulip Catherine Hosage Norman (Nov 03 2020 at 18:34):

That is the IDMP use case. We are adapting to this via our profiles.


Last updated: Apr 12 2022 at 19:14 UTC