Stream: implementers
Topic: Wristband-driven Data Collection
Kevin O'Donnell (Feb 27 2019 at 21:16):
Thanks to all for the input on the prior queries. Based on that, I'm going to back up a step to a more open question.
Consider the lightweight (i.e. relatively dumb) data collection devices in the hospital that are either carried from patient to patient, or are in an exam room where patients come through one by one. The data they collect (a photo of a lesion, a blood sugar reading, etc) needs to be associated with the correct patient/encounter. Most hospitals put wristbands on patients that have a patient name and/or visit number and/or patient id, etc (encoded as a barcode, QR code, RFID, or just plain text), in part to facilitate this kind of thing.
What is the current thinking about how such a (dumb) device should proceed?
John Moehrke (Feb 27 2019 at 21:32):
IHE has a profile for this -- https://wiki.ihe.net/index.php/Uniform_Barcode_Processing
It leverages FHIR and GS1
Grahame Grieve (Mar 01 2019 at 22:20):
in general, there'll be some gateway device/process that unites the observations they produce with the patient id
Kevin O'Donnell (Mar 02 2019 at 01:40):
Agreed. We (IHE Rad) are trying to profile those gateway devices/processes for our use case. Currently, it is common for photos to only be associated with the patient id which clinicians find very frustrating (the dreaded "Media tab" in the EMR), so in addition to associating with the patient id, they've asked us to also associate with details such as the current departmental encounter and the admission encounter to which that belongs, the device, operator, etc.
So from @John Moehrke, I get the first part...
Step 1: Scan patient wristband
Step 2: Transmit scan-string to Barcode Processor
Step 3: if it's a patient id, the Barcode Processor will recognize it as such because ...? and return a Resource containing a Patient.identifier
Step 4: If it's a visit/account number, the Barcode Processor will recognize it as such because ...? and ...?
Step ...?
Step N: Store photo with metadata/linkages to the patient id, admission, department encounter, device, operator, etc.
Grahame Grieve (Mar 02 2019 at 05:13):
have you looked at the POC FHIR Igs from the Devices workgroup? I believe that this is something they deal with
Jose Costa Teixeira (Mar 30 2019 at 19:05):
Barcode processor recognizes codes assuming that the codes are enabled to do that. Some barcoding schemes have their semantics.
Jose Costa Teixeira (Mar 30 2019 at 19:06):
e.g. if a barcode starts with 01, it's a product
Jose Costa Teixeira (Mar 30 2019 at 19:08):
if a barcode has just a uuid, the barcode processor will have a harder time (and so may the patient) - something else is needed e.g. a lookup
Last updated: Apr 12 2022 at 19:14 UTC
