MCI forms and barcodes

Simusid

Forum Captain
Messages
336
Reaction score
0
Points
16
I am using this form http://en.wikipedia.org/wiki/File:SmartTag_TriageTag.jpg and I've been unsuccessful at reading the barcode using the ZXing barcode app (that apparently supports the most popular barcode formats)

If anyone here happens to have a Droid or an iPhone as well as this MCI form would you mind trying to scan it too? Let me know if it works or fails. Thx!
 
I am using this form http://en.wikipedia.org/wiki/File:SmartTag_TriageTag.jpg and I've been unsuccessful at reading the barcode using the ZXing barcode app (that apparently supports the most popular barcode formats)

If anyone here happens to have a Droid or an iPhone as well as this MCI form would you mind trying to scan it too? Let me know if it works or fails. Thx!

I don't have any of these tags, but I use RedLaser if I ever need to scan a 2D/3D barcode with my phone.
 
thanks I did try redlaser. It was able to read the barcode once with great difficulty but not a second time. It may be my phone. I think the earlier droids had camera focus problems.
 
What's the purpose of using the barcode?


Sent from my iPhone using Tapatalk
 
when you have an MCI you can scan the initial injury level, then the TTT barcodes once they clear those areas, which allows you to track patients from initial contact to transfer of care at the hospital, using phone allows everyone to do this easier
 
when you have an MCI you can scan the initial injury level, then the TTT barcodes once they clear those areas, which allows you to track patients from initial contact to transfer of care at the hospital, using phone allows everyone to do this easier
Barcodes are just a graphical representation of data (numbers and letters). What are you scanning the barcode into? Otherwise you're just decoding a number or letter sequence.
 
As usual, beware the use of personal communication devices in regards to HIPAA violations. Most agencies have a policy against storing or using protected information in conjunction /c personal communication devices. How are you using this information? You cell phone isn't an agency phone is it?


I'm not admonishing you, just giving you the warning. People have gotten fired from my network for taking pictures of things like detached eyeballs and what not.
 
Barcodes are just a graphical representation of data (numbers and letters). What are you scanning the barcode into? Otherwise you're just decoding a number or letter sequence.

I am considering writing a web based app that allows a user to triage a patient on an iPhone or Droid (I write for both). I have seen apps that do this but not one that will easily xfer the data to a central database so all participants in an MCI can see the status of all patients. Example, the triage officer could scan the tag he was handed, scan the bar code and see that the patient was transported to Hospital XYZ.

My inquiry here was to see if others had as much trouble scanning the SMART tags as I did. I can handle the coding :)
 
I have to agree with 8jimi8 on this one. You would be entering a lot of personal information and passing it over cell frequencies. If any of that information gets out to the general public you could very well violate HIPPA laws. This also creates another step in the process dealing with an MCI. If you have never been to an MCI the scene is absolute Chaos. Adding another step IMO would be useless.
 
I also think SMART has a whole suite of bar code readers and software already made up for MCI management... and you might be better off contacting them, and seeing if you can contract to make smartphone versions of their existing work than re-inventing the wheel...
 
As usual, beware the use of personal communication devices in regards to HIPAA violations. Most agencies have a policy against storing or using protected information in conjunction /c personal communication devices. How are you using this information? You cell phone isn't an agency phone is it?


I'm not admonishing you, just giving you the warning. People have gotten fired from my network for taking pictures of things like detached eyeballs and what not.


Actually, some of our phones are agency phones. I'd have no problem expanding that to our other members. I completely understand the sensitivity of taking patient photos and we nearly fired one employee for such an incident that violated our existing photo policy.

Yes, I'm fully aware that this could involve HIPAA data. Both the Android and iOS platforms support strong encryption for transmission, and that meets the HIPAA requirements. Our existing servers are HIPAA compliant as well though they are not public facing, so opening a webserver to the internet would be a bit more of a challenge (but not much).

I agree these are all serious concerns, but not to the point that you would say "oh this is too hard, lets not do it"
 
I am considering writing a web based app that allows a user to triage a patient on an iPhone or Droid (I write for both). I have seen apps that do this but not one that will easily xfer the data to a central database so all participants in an MCI can see the status of all patients. Example, the triage officer could scan the tag he was handed, scan the bar code and see that the patient was transported to Hospital XYZ.

My inquiry here was to see if others had as much trouble scanning the SMART tags as I did. I can handle the coding :)

I'm confused about what you're describing here in terms of triaging a patient on an iPhone or Android. So providers triage patients with a fairly traditional triage tag (that has a barcode) and then need to also enter their triage designation into a mobile device?

I don't doubt that you can code the app, but I question the true practical application of what you're suggesting at this point in time.
 
I'm confused about what you're describing here in terms of triaging a patient on an iPhone or Android. So providers triage patients with a fairly traditional triage tag (that has a barcode) and then need to also enter their triage designation into a mobile device?

I don't doubt that you can code the app, but I question the true practical application of what you're suggesting at this point in time.

A very fair point. Maybe what I'm thinking of really would not help. My area is hospital-rich, with at least 7 hospitals within a 20 minute drive. One is pediatric, one is a level 1 trauma center, one is a stroke center, etc. Plus a burn center within about an hour.

During patient triage, I wanted the medic to scan the triage barcode and indicate the very basic info about the patient including transport destination. The triage officer has the other half of the tag and would scan his copy to find out where a patient went. I was hoping that it would be easier to answer questions regarding location of patients, particularly john/jane doe's.
 
At an MCI, the defecation has hit the ventilation and you need to assume that if a piece of equipment can break, it will. That's why we stick to low-tech, simple technology, and that's why pen and paper works so well. I encourage you to keep this mind, and always keep a low-tech backup.

Sent from my DROID2 using Tapatalk
 
A very fair point. Maybe what I'm thinking of really would not help. My area is hospital-rich, with at least 7 hospitals within a 20 minute drive. One is pediatric, one is a level 1 trauma center, one is a stroke center, etc. Plus a burn center within about an hour.

During patient triage, I wanted the medic to scan the triage barcode and indicate the very basic info about the patient including transport destination. The triage officer has the other half of the tag and would scan his copy to find out where a patient went. I was hoping that it would be easier to answer questions regarding location of patients, particularly john/jane doe's.

I'm still not entirely sure whether I've understood how this will be put into practice, but here are a few key issues:
- You say that when the patient is being triaged, the medic triaging would also scan the barcode and then enter additional information into the device. This adds on significant time. Even a 10 second addition to a process that should only take 30 seconds adds up.
- When the patient is being triaged, their ultimate destination won't likely be known. This will be up to the Transport Officer. Nothing is easy at at MCI, but as long as everyone respects the Transport Officer's role then this patient destination tracking should be relatively straightforward.
- Will every agency who may be triaging patients (i.e. everyone with EMS resources anywhere in the region who might potentially respond to an MCI together) get on board with this? If not, it is useless.
- Even with agency phones, the lack of devices could make this ineffective. Let's say we have an MCI. The first crew arrives and one crew member takes the command role while the other begins to triage. Just after the first crew arrives, a second arrives. Both of these crew members begin to help with triage. This requires that this crew has been issued two phones. I suspect that many agencies would issue one phone per ambulance. So does one guy just need to sit out and wait for his two colleagues to finish triage? That is not effective use of resources.
- How will the issues of contamination be addressed? It doesn't seem practical to wipe down the phone between patients. Will touch screen devices even respond when being used by someone with medical gloves?

I commend you for trying, but I think your coding skills may better be spent elsewhere. I don't doubt that you can code something, and maybe even manage to sell it to a few agencies. But I just don't think that it would be truly beneficial in the field at this point.
 
At an MCI, the defecation has hit the ventilation and you need to assume that if a piece of equipment can break, it will. That's why we stick to low-tech, simple technology, and that's why pen and paper works so well. I encourage you to keep this mind, and always keep a low-tech backup.

Sent from my DROID2 using Tapatalk
Or the batteries will be dead.
 
I'm still not entirely sure whether I've understood how this will be put into practice, but here are a few key issues:
- You say that when the patient is being triaged, the medic triaging would also scan the barcode and then enter additional information into the device. This adds on significant time. Even a 10 second addition to a process that should only take 30 seconds adds up.
- When the patient is being triaged, their ultimate destination won't likely be known. This will be up to the Transport Officer. Nothing is easy at at MCI, but as long as everyone respects the Transport Officer's role then this patient destination tracking should be relatively straightforward.
- Will every agency who may be triaging patients (i.e. everyone with EMS resources anywhere in the region who might potentially respond to an MCI together) get on board with this? If not, it is useless.
- Even with agency phones, the lack of devices could make this ineffective. Let's say we have an MCI. The first crew arrives and one crew member takes the command role while the other begins to triage. Just after the first crew arrives, a second arrives. Both of these crew members begin to help with triage. This requires that this crew has been issued two phones. I suspect that many agencies would issue one phone per ambulance. So does one guy just need to sit out and wait for his two colleagues to finish triage? That is not effective use of resources.
- How will the issues of contamination be addressed? It doesn't seem practical to wipe down the phone between patients. Will touch screen devices even respond when being used by someone with medical gloves?

I commend you for trying, but I think your coding skills may better be spent elsewhere. I don't doubt that you can code something, and maybe even manage to sell it to a few agencies. But I just don't think that it would be truly beneficial in the field at this point.

These are all very good operational points and clearly I cannot say that I have any answers. I originally thought this would be useful because every MCI form I have seen already has a barcode, so I *assumed* that this supported existing processes. Nobody I know (in the 11 surrounding towns) has dedicated MCI barcode scanners, so I figured I'd be filling a need, not trying to address a non-problem!

I agree, I'll try to code something else more useful for EMS!
 
These are all very good operational points and clearly I cannot say that I have any answers. I originally thought this would be useful because every MCI form I have seen already has a barcode, so I *assumed* that this supported existing processes. Nobody I know (in the 11 surrounding towns) has dedicated MCI barcode scanners, so I figured I'd be filling a need, not trying to address a non-problem!

I agree, I'll try to code something else more useful for EMS!

AFAIK, they're kept in the regional MCI trailers (MBEMSC or SEMAEMS), which can be activated through CMED and are generally kept at hospitals or centrally located fire departments. The idea is that they can be mobilized to a scene in just a few minutes.
 
not to change subjects...

In regards to HIPAA & MCI's...doesn't the rules kinda change (for lack of a better term), at least for the purposes of make proper identification of (living or dead) bodies, reuniting families, etc? (I'm talking a real MCI, not a MVA w/ 1 Ambulance & 6 patients...we're talking plane/train crash, natural disaster, etc)

And our MCI/triage tags have several bar-codes on them (identical), stickers, so you can attach them to charts, etc.
 
Back
Top