Stakeholders : It is assumed that a gamut of self sufficient bodies are responsible for the access of a Patient's Medical History. These bodies include Hospitals, Specialty treatment facilities, Health Insurance Organizations, Financing institutions, External Agencies and the patient himself
Record Distribution : From the given scenario, it is evident that the patient's medical records are distributed over an array of system hardware such as decentralized server systems of possibly different hardware architectures.
Record Access : The various stakeholders involved may need to access the records while emanating from different platforms such as Desktop Systems, Laptops, Personal Digital Assistants, Mobile Phones. The Records access medium such as the Internet for example will facilitate a form of common record access to these disparate systems.
Record Compatibility : Compatibility being one of the core issues that govern the scenario, it is assumed that the records are not system dependent, but rather it is said to be a common abstractive entity that can exist and be transmitted between different software environments.
Record Types : The origination of records are itself of two types, from a medical perspective, i.e "Born digital" and "Scanned records". While the former type is a record that has itself been created digitally, the latter is one where the records may be scanned from the patient's X-Rays, Photographs etc.
Record Redundancy : Due to certain unforeseen and inevitable data mismanagement by the various stakeholders involved with the patient, a degree of redundancy is assumed to be observed within the patient's medical records.
Availability of Data Repository : Since such databases of the patient, may involve saving the life of the concerned patient, it is assumed that the data repository must be available and accessible at all times and at all costs. There must be zero tolerance towards System failure. For this reason, resilient hardware and software technologies are used to ensure that the data is available at all times.
3. Ideal PMR (Patient Medical Records) Architecture
1. Location Of Data :
A Centralized Server with network access clients, which will the use standard Windows 2003 Server or a Linux Distribution, is used to hold the PMR Server software suite. It is mandatory that the server uses a resilient and high bandwidth network backbone such as ISDN, and the server system must be specifically used for Medical Database Hosting and management. The location of such a server is entrusted with any national or public sector health institution, that is capable of maintaining a huge database of the patient's medical records.
The institution must also provide access services to the patient's authorized stakeholders and also at the same time, be responsible in handling and tracking the patient's progress from its data repository and knowledge base.
2. Medical Record Services :
The PMR software must allow access, modification and updates over