UnitCode problems when used as unit of dosage

Question

UnitCode problems when used as unit of dosage

Closed this issue 7 months ago · 19 comments

Our problem:

There are two semantically different units to be used: units of presentation (what comes in the packaging/article) and units of administration (units suitable to express drug intake/administration). At present, CH EMED uses, besides the UCUM codes, only the SNOMED codes for unit of presentation for both cases (e.g. Medication.amount through CHEMEDRatioWithEmedUnits fields numerator and denominator being CHEMEDQuantityWithEmedUnits which have the code bound to UnitCode). Now, for instance, in the case of a treatment with an inhaler, the unit of presentation would be, as it is the case now, code 732997007 i.e. Inhaler. Now if the planned dosage is to be twice inhalations per day, we cannot use the same unit, since that would mean that the intake is 2 inhalers per day and not two inhalations. For this, SNOMED has codes for unit of drug administration: https://browser.ihtsdotools.org/?perspective=full&conceptId1=408103002 which would allow us to use for this example the code 422237004 for Inhalation (https://browser.ihtsdotools.org/?perspective=full&conceptId1=422237004).

Proposal:

Keep the medication resource as is, using CHEMEDRatioWithEmedUnits for the amount field.
Keep CHEMEDRatioWithEmedUnits using CHEMEDQuantityWithEmedUnits for both numerator and denominator fields but rename it to something like CHEMEDRatioWithEmedPresentationUnits.
Rename UnitCode to PresentationUnitCode.
Rename CHEMEDQuantityWithEmedUnits to CHEMEDQuantityWithEmedPresentationUnits.
Add new value set AdministrationUnitCode or DoseUnitCode with the same UCUM codes but using the SNOMED codes from https://browser.ihtsdotools.org/?perspective=full&conceptId1=408102007 instead.
Add the data type CHEMEDQuantityWithEmedDoseUnits with code bound to DoseUnitCode.
Rename CHEMEDRangeWithEmedUnits to CHEMEDRangeWithEmedDoseUnits and change low and high fields to use CHEMEDQuantityWithEmedDoseUnits.
Replace CHEMEDQuantityWithEmedUnits with CHEMEDQuantityWithEmedDoseUnits in the dosage data types:
- CHEMEDDosage.doseAndRate.doseQuantity
- CHEMEDDosageSplit.doseAndRate.doseQuantity

I hope this is clear but let me know what you think or if something is not clear or if I can provide anything else to help.

Answer 1 · 2023-11-10T13:26:20.000Z

@dvribeira
I tried to make an overview of the usage of the units with your proposal. Could you please have a look, if I understood your proposal the correct way?

Answer 2 · 2023-11-15T10:50:08.000Z

I somehow missed the notification 5 days ago. I will have a look first thing this afternoon. Thanks a lot!

Answer 3 · 2023-11-15T13:44:22.000Z

@ziegm The proposal is well summarized in the spreadsheet. Perhaps the example I provided is not the best since one could use either inhalation (administration) or indeed actuation (presentation) to express the dosage. Perhaps it would be more tricky for an applicator for which we would have application in the units of administration for instance for https://compendium.ch/product/1510171-bepanthen-med-creme and a very difficult choice on the current UnitCode.

Thanks!

Answer 4 · 2023-11-15T13:57:25.000Z

@dvribeira May you could add the example in the sheet?

Answer 5 · 2023-11-15T14:56:34.000Z

@ziegm I have added two examples that I hope are of use by using the data on the HCI indices.

Answer 6 · 2023-11-16T12:50:45.000Z

16.11.2023 PJ/OE/MZ:

Evaluation/Discussion:

Var 1: Proposal from this issue
Var 2: stay with 1 VS and add additional codes

Next step: Integrate a proposal for Var 1 in the next release (v5.0.0-ballot) and collect feedback from the implementers

Answer 7 · 2023-11-29T15:45:32.000Z

I know this will not be part of 4.0.0 but in any case I would ask to put this on hold for a while (if we are the only requestors). After another meeting for feedback with a pharmacist we have found that it seems the second set of SNOMED codes (the ones for administration) would also be incomplete after all (at least for what it concerns HUG's PRESCO application). I am trying to get a more complete view of each CARA PMP involved implementer's needs on this in the hopes I can finally get a proper view. In the meantime I apologize for any possible wasted effort and ask not to proceed with this for now.

Once I manage to gain a better understanding of the other system's needs I will get back to this issue.

Thanks a lot :)

Answer 8 · 2024-01-04T15:06:18.000Z

@dvribeira
As we are already starting to work on the ballot version, I'd like to know where you are standing on this issue, because you asked to put it on hold. Thx!

Answer 9 · 2024-01-10T13:25:56.000Z

@ziegm Sorry for the delay, I have returned from my holidays only today. I managed to get feedback from all the involved implementers only just before the Christmas holidays, so I didn't have time yet to fully address this on our side. However, I can say that:

It seems we would still be missing some important units in the SNOMED units of administration set.
If we would have to also complete units of administration then we could live with just completing the current UnitCode value set with what's missing and not separating in two value sets. This should be easier for implementers.

I do not think I will find the time to work on this on what's left of the week, but I hope to work on this next week. Since this work will entail also discussions it might still take a while until I can provide more refined (and more final) feedback on this: I wish to firmly establish which units are needed and how to map them for all the actors involved.

In the meantime: how feasible do you think it would be to add values to UnitCode that are not currently in neither of the aforementioned SNOMED sets?

Many thanks!
Daniel

Answer 10 · 2024-03-21T12:37:39.000Z

From the units in Code type 9 from HCI index, it seems nmol would be missing and also I am not sure about the following:
Pfl Pflaster patch -> 733010002 pflaster|plaster|emplâtre or 733005001 patch|patch|patch ?
Teilpck Teilpackung emballage individuel -> 1681000175101 package ?

For the mapping of units of the prescription software of HUG, we would miss application as in applying a creme.

Answer 11 · 2024-03-21T12:44:45.000Z

21.03.2024 PJ, DV, QL, MZ, AB

units are missing:
- UCUM: nmol (nanomole)
- SCT 413568008 | Application - unit of product usage (qualifier value) (@pjolo check with @PeroGrgic )
add it to https://build.fhir.org/ig/hl7ch/ch-epr-term/ValueSet-UnitCode.html

Answer 12 · 2024-03-26T12:37:08.000Z

@ziegm

Do I have to insert the code nmol (nanomole) in ArtDecor or can this be done directly in CH Term?
The SNOMED code 413568008 | Application - unit of product usage (qualifier value) can be included. For the translations, it must be checked if there is enough time for the Swiss extension release.

Answer 13 · 2024-03-26T12:53:10.000Z

@ziegm

Do I have to insert the code nmol (nanomole) in ArtDecor or can this be done directly in CH Term?

The SNOMED code 413568008 | Application - unit of product usage (qualifier value) can be included. For the translations, it must be checked if there is enough time for the Swiss extension release.

@pjolo yes please, include both in art decor

Answer 14 · 2024-03-26T15:04:59.000Z

@ziegm I have included both codes

Answer 15 · 2024-03-26T15:13:44.000Z

@oliveregger could you please update the import of the CH Term VS from Art-Decor?

Answer 16 · 2024-03-27T17:06:51.000Z

@ziegm see PR above

Answer 17 · 2024-03-28T11:15:20.000Z

@dvribeira @pjolo you can review the changes:

CH Term
- VS UnitCode
- Changelog
CH EMED
- Changelog

Answer 18 · 2024-03-28T12:07:41.000Z

From my side the changes are good

Answer 19 · 2024-04-03T07:38:04.000Z

Good for me too. Thanks!