Dear PCORnet OMOPPERs,
I’ll also post this on the OHDSI forum but didn’t know if
you monitor that and those in our project are not in that community.
We have a PCORnet rapid cycle research project for cancer and
one element is to incorporate or link chemotherapy for targeted therapeutics across
sites in MidSouth, GPC, and OneFlorida.
We plan to push the infusions into the PCORnet CDM4.0 draft
for MED_ADMIN table and pilot a couple columns to resolve some ambiguities.
One field we want to add is a concept code ala OMOP to distinguish the type of administration and we were inspired by the OMOP drug_type_concept_id
It looks like if I browse Athena, I can find your current
but it’s not totally clear to me what your community would call chemotherapy infusion in a cancer treatment room.
A OHDSI thread at one point indicates inpatient but then in other ways isn’t clear to me.
I don’t consider that to be an inpatient unit but it’s also not administered by the physician. It’s definitely not based on the Jcode procedure as that kind of data will be placed in the PROCEDURE table for the CDM
But, I don’t know if your community just always says they are physician administered based on an EHR order (581373), physician administered from an EHR observation (43542358), or takes a big tent healthsystem
view of inpatient administration (38000180). Same would go for emergency rooms as well I suppose.
I’d call it something like “clinic infusion room administration” as a new concept and then perhaps have other concepts for med admin not done by a physician in other procedural areas but since you don’t choices like that in your vocabulary I’d love to know why before we create concepts orthogonal to your work.
Thank you for your guidance as we’d like to be aligned with
as broad a part of PCORnet as possible across these data models.
2. The other fields we see as valuable to pilot would be
a. PRESCRIBING_ID (a link back to the PRESCRIBING table which should contain the parent medication order from the physician for the chemotherapy)
b. MEDADMIN_DOSE_CALCULATED – using the same field to store strength or dose is suboptimal in terms of
clarity of the current 4.0 draft (MEDADMIN_STRENGTH_CALCULATED). The actual dose received is more important to
us than the strength of the infusion bag/pb.
c. MEDADMIN_DOSE_CALCULATED_UNIT –ditto
Potentially (not critical to this study but we see some use cases where having the start and stop of the infusion session could be useful):
d. MEDADMIN_DATE as MEDADMIN_START_DATE
e. MEDADMIN_TIME as MEDADMIN_START_TIME
Russ Waitman, PhD
Director of Medical Informatics
Associate Vice Chancellor for Enterprise Analytics
Professor, Department of Internal Medicine
University of Kansas Medical Center, Kansas City, Kansas
http://www.gpcnetwork.org – a PCORnet collaborative