Skip to main content

The case for PAA














PAA stands for Patient Admission App. In a nutshell it is a platform in which the hospital can communicate with its patients and their relatives before, during and after their stay in  the hospital.

A patient's encounter with a hospital is often a traumatic event to both the patient and his family. A lack of  proper communication between the parties can have major implications on the hospital efficiency and the patient's experience which research shows has a critical impact on the quality of care.

From red tape to red carpet 

A PAA should accompany the patient throughout his journey by keeping him informed and engaged. This starts prior to the actual admission when the patient feels scared, anxious and confused. A PAA should provide the patient with all the information related to his upcoming treatment. This can include treatment reminders such as not to eat x hours before a planned anesthesia, orientation map, etc. It should also handle in advance all the bureaucratic routines, such as filling up a pre-anesthesia assessment and submitting a consent form, in order to insure a smooth admission process.

Information is a cure to the mind 

During the hospital stay there is often an information gap between the patient and the care givers. The patient feels lack of control and is in constant and exhausting pursuit after information. 
A PAA mitigate that information gap by integrating with the clinical systems in use by the care team and exposing to the patient the information the care team would like to share as soon as it is made available. This includes items such as the patient's treatment plan, screening assessments and new lab results that are ready.

A safety net to improve patient safety 

Providing the patient with access to the data recorded in his medical record can reduce errors which are the results of miscommunication and simple human mistakes. By reviewing his record, the patient can validate that important information such as known allergies, home medications, and medical history are accurately recorded and that the care team is basing their decisions on a correct and up to date information.

Recovery is part of the treatment

Back at home, when the care team is no longer around, the patient often feels confused, helpless and disengaged. As a results, the patient is prone to fail following the instructions given to him at discharge such as the medications to take and follow up appointments. A PAA should come to rescue at this stage as well as by providing post care education and  treatment reminders. In addition, the data captured during the stay can be shared with the GP and help future treatment and consultation.

Lastly, a PAA should allow the patient to fill a satisfactory survey to let the hospital know what can be improved, or to simply say thank you.

Comments

Popular posts from this blog

Clinical data warehouses: Sometimes it's worth being lazy

If you are a health organization you probably have or thinking of having a clinical data warehouse. A Clinical Data Warehouse (CDW), sometimes called Clinical Data Repository (CDR), is a database that consolidates data from a variety of clinical sources to form a unified view of a the data for various purposes. Typical data types which are often found within a CDW include: clinical laboratory test results, vital signs, patient demographics, administered meds, hospital admissions, ICD-9 codes and more. Developing and sustaining an effective CDW operations unit is a substantial effort and long-term commitment. The main challenge in designing a CDW is defining its scope and the use cases it should support. In theory a CDW can serve as a basis for reporting, studying and planning. The use case that is often mentioned in relate to CDW is supporting clinical trials. This would allow for researchers to have all the information from a study in one place as well as let other researchers benefit

The big battle: Best of breed vs One stop shop

The world of economics has decided on this debate a long time ago: monopolies are bad, diversity is good. No matter what a monopoly promises, you can rest assure that over time the lack of competition will cause prices to go up and quality to go down. When it comes to healthcare IT, however, there is one unique factor that flips the coin – interoperability. Despite various attempts the healthcare industry has yet to solve the interoperability challenge in a satisfactory manner which will enable a full continuum of care across different health information systems within a health delivery organization. Taking a common scenario of prescribing a medication order in theatres using a surgical system to be later administered in a ward requires significant investment to achieve, even using the modern Fast Health Interoperability Resource (FHIR) protocol. The investment required to streamline the data flow across systems raise in an exponential order with every new system that is thrown to t

Are we ready for a Cloud First hospital?

I will start this article by defining what I mean by the term a Cloud First hospital. The term cloud has been a buzz word in the past decade which led many organizations to declare their support for the cloud, sometime without understanding its true meaning. For the purpose of this article I am proposing a simple test to decide whether an organization is a cloud first or not. If you are software vendor you must have an IT department which directly in charge of the system up-time at your clients sites. If you are a health organization then you should never have visited the data center where your data resides. A Cloud First hospital is one which more than 50% of its systems reside in data center that none of its staff members ever visited or not even sure where they are. According to a recent survey by Datica, in the US only 17.7 percent of the respondents say they work with healthcare organizations that have more than 50% of the existing software infrastructure remotely hosted or