Keith I enclose a spreadsheet with my mappings to route and admin_units that each include a frequency of occurrence in our Epic system. I would have to say that the valuesets that were distributed with CDMV4 were difficult to interpret and I think it would be an advantage to interoperation to be a lot more specific with the guidance and a generous set of exemplars.
My final conclusion on DIALYSIS was to use INTRAVASCULAR; I kept INJECTION.
For units, I think that UCUM is weird when I have to code TABLET as
NUMBER{tablet}.
Jim
From: Marsolo, Keith [mailto:keith.mars...@cchmc.org]
Sent: Friday, March 23, 2018 7:11 AM
To: Campbell, James R <campb...@unmc.edu>
Cc: allison.hauf...@duke.edu; Pedersen, Jay G <jay.peder...@unmc.edu>;
gpc-dev@listserv.kumc.edu; Campbell, Walter S <wcamp...@unmc.edu>; Vreeman,
Daniel J <dvree...@regenstrief.org>; michelle.sme...@duke.edu; Katie Arnold
<katherine.arn...@duke.edu>
Subject: Re: MED_ADMIN route and units codes
Non-UNMC email
Jim,
These are great questions. Thanks for sending.
We’re using SNOMED for the routes of administration, since that’s what’s
associated with RXNORM, but as you’ve discovered, it’s not the friendliest
value set. This may be something that we look to revise in the future.
Based on your source data, if it’s possible to figure out where the medication
was administered, you should map it to the appropriate SNOMED code. If there’s
any ambiguity, then you should map to OT and put the source value in the RAW
field. For instance, an Injection could map to the Subcutaneous or
Intramuscular or Intraocular, depending on the drug, so that’s probably a good
candidate for OT.
As for the units, we’re leveraging the common UCUM units as identified by LOINC:
https://loinc.org/usage/units/
The universe of UCUM codes is essentially unbounded
(http://unitsofmeasure.org/ucum.html#datyp2apdxatblxmp), so unless we want to
change the unit field type to text, we have to have a finite list in order to
test conformance (you could imagine a program that might “compute” whether a
unit was valid based on the UCUM rules, but that’s out of our scope for the
time being).
UNIT, DROP and EACH fall into the existing value set, so you should be able to
handle those. The remaining units would be mapped to OT with the source value
in the RAW field. The other question I’d ask is whether you have a sense of
how prevalent those codes are across your source data. Things like tablet,
capsule and puff are typically used to represent medication dose form, so I
wouldn’t necessarily expect to see them labeled as units (though technically
they can be).
Thanks.
Keith
On Mar 20, 2018, at 1:43 PM, Campbell, James R
<campb...@unmc.edu<mailto:campb...@unmc.edu>> wrote:
Thanks to Alex Stoddard to suggest that the valuesets published by PCORNET are
not all-inclusive. Looking to the UCUM site for guidance on units codes, it
appears that some of the units of administration might be:
Tablet = NUMBER{tbl}
Capsule = NUMBER{capsule}
Drop = VOLUME{drp]
Ampule = VOLUME{ampule}
Puff = VOLUME{puff}
Spray = VOLUME{spray}
Each = NUMBER
Units = [IU]
Jim Campbell
From: Gpc-dev [mailto:gpc-dev-boun...@listserv.kumc.edu] On Behalf Of Campbell,
James R
Sent: Tuesday, March 20, 2018 9:53 AM
To: Keith Marsolo <keith.mars...@cchmc.org<mailto:keith.mars...@cchmc.org>>;
allison.hauf...@duke.edu<mailto:allison.hauf...@duke.edu>
Cc: Pedersen, Jay G <jay.peder...@unmc.edu<mailto:jay.peder...@unmc.edu>>;
gpc-dev@listserv.kumc.edu<mailto:gpc-dev@listserv.kumc.edu>; Campbell, Walter S
<wcamp...@unmc.edu<mailto:wcamp...@unmc.edu>>
Subject: MED_ADMIN route and units codes
Non-UNMC email
Keith
Allison
For routes, I cannot code 'Dialysis', 'Infiltration' and 'Injection' and must
use OT?
I cannot locate UCUM for these units:
CASE WHEN O.HV_DOSE_UNIT_C = 5002 THEN 'tablet'
WHEN O.HV_DOSE_UNIT_C = 5006 THEN 'puff'
WHEN O.HV_DOSE_UNIT_C = 5004 THEN 'drop'
WHEN O.HV_DOSE_UNIT_C = 5013 THEN 'ampule'
WHEN O.HV_DOSE_UNIT_C = 5003 THEN 'capsule'
WHEN O.HV_DOSE_UNIT_C = 5008 THEN 'spray'
WHEN O.HV_DOSE_UNIT_C = 5 THEN 'Units'
WHEN O.HV_DOSE_UNIT_C = 5001 THEN 'each'
Jim Campbell
The information in this e-mail may be privileged and confidential, intended
only for the use of the addressee(s) above. Any unauthorized use or disclosure
of this information is prohibited. If you have received this e-mail by mistake,
please delete it and immediately contact the sender.
The information in this e-mail may be privileged and confidential, intended
only for the use of the addressee(s) above. Any unauthorized use or disclosure
of this information is prohibited. If you have received this e-mail by mistake,
please delete it and immediately contact the sender.
The information in this e-mail may be privileged and confidential, intended
only for the use of the addressee(s) above. Any unauthorized use or disclosure
of this information is prohibited. If you have received this e-mail by mistake,
please delete it and immediately contact the sender.
ROUTE_ADMIN_MAP.xlsx
Description: ROUTE_ADMIN_MAP.xlsx
_______________________________________________ Gpc-dev mailing list Gpc-dev@listserv.kumc.edu http://listserv.kumc.edu/mailman/listinfo/gpc-dev
