Many Health IT folks say to never ever allow test patients in prod, but very rarely there is no other option. Most EHRs have the ability to flag patients as test so there are no billing or interface problems. Also, an organization can make sure patients have a last name of something like XYZTEST. Then they can block any interface messages for those records in the interface engine.
Doug P - 9 years ago
This is a risk due to all the interfaces to Downstream systems and even system external to the hospital. Also, based on rules, things can be produced such as printouts that users may act on thinking the patient is real which is why if we do allow this it's with patients that are tagged so they don't produce bills, printouts or skew reporting.
Bruce Slater - 9 years ago
this would be very helpful, but for financial reasons, it is risky
I would support it with strict rules about how to use them and strong protections to prevent real charges dropped.
Many Health IT folks say to never ever allow test patients in prod, but very rarely there is no other option. Most EHRs have the ability to flag patients as test so there are no billing or interface problems. Also, an organization can make sure patients have a last name of something like XYZTEST. Then they can block any interface messages for those records in the interface engine.
This is a risk due to all the interfaces to Downstream systems and even system external to the hospital. Also, based on rules, things can be produced such as printouts that users may act on thinking the patient is real which is why if we do allow this it's with patients that are tagged so they don't produce bills, printouts or skew reporting.
this would be very helpful, but for financial reasons, it is risky
I would support it with strict rules about how to use them and strong protections to prevent real charges dropped.