Ranjan Dailata I understand where you are coming from but one thing I am definitely not trying to do is to create a new EMR. It is the exact problem that I am trying NOT to solve.
The problem we are trying to solve is updating everyone involved in the process of surgery where the patient is and giving them a forum to discuss things that need to be completed for the patient before they go in for surgery and letting family know updates about the patient. The name of the game in Peri-Op is to get the patient in on time and knowing where the patient is can help facilitate that. This doesn’t require the entire patient medical library. This would be more similar to a bed-board related function.
The minimum to make this work would be the Patient identifiers, the type of surgery they are going for, the surgeon, the operating room, and maybe allergies. I don’t want to touch the existing systems used for keeping the medical information, at least not yet. Each one of the systems that they use already exist within a silo. Having the ability to retrieve this info would be helpful after the interface of communication could be established and made very user friendly for everyone involved. I imagine this would be sort of like a premium version of the app I want to offer that could solicit all of this info.
I am trying to avoid touching the existing EMRs for the precise reason you are mentioning because finding a way to get all of that data would be a big undertaking unless there is someway to create something that would easily extract this info. This is all based on my hospital and several other hospitals I know in NYC and some ambi centers that have some very archaic ways of tracking there patients through the process. My hospital still literally uses a list they print out every day that they have to manually enter into an excel sheet. It is a clip board that everyone has to look at when they walk into the pre-op area.
Does this help to clear up what I am trying and not trying to do?