Figure 6 - uploaded by María Mercedes Larrondo Petrie
Content may be subject to copyright.
Source publication
We discuss analysis patterns that describe some aspects of recording information in a medical system for patient treatment. The Patient Treatment Records pattern includes two simpler patterns that describe the creation and maintenance of the patient record and the assignment of the hospital assets for use by the patient. The Patient Record pattern...
Context in source publication
Context 1
... assets of the medical group are organized in a hierarchical arrangement that describes their physical or administrative structure. Class diagram for Asset Assignment Figure 6 shows a sequence diagram for assigning assets to an inpatient, the location where the patient will be treated is checked for availability and assigned to the patient. After that, doctors and nurses are assigned. ...
Citations
... The doctor will reason by linking the health problems to the symptoms, the clinical signs and the observations in order to propose health care procedures. The software system can thus rely on the SOAP model (Subjective, Objective, Assessment, Plan) used by the medical community [18]. In this model the S nodes describe current symptoms and clinical signs of the patient, the O nodes describe medical tests, analyses or observations of the physician, the A nodes correspond to the diseases or health problems of the patient, and the P nodes correspond to the procedures or action plans set up in order to solve the health problems. ...
The paper presents a framework for a distributed medical system meant to bring a modern approach and inhance the quality of medical services offered to chronicle patients with cardio-vascular diseases, through the latest IT&C technologies. The proposed system provides online interaction between the main actors of a medical system: patients, doctors, medical entities (e.g. hospitals, clinics) and medical authorities (e.g. social services). With the aid of widely accepted medical standards, the system supplies storage for medical records and offers services for data integration between different kinds of healthcare applications and entities. The proposed ontological approach allows interchange of medical knowledge and best practices with conceptually organized patients’ records. The proposed solution allows computer assisted diagnoses and multi-criteria medical data analysis, with the possible extent of building a data warehouse for complex medical data mining.
In the past , medical information was physically stored in hospitals, laboratories, and doctors' offices. A ccess to this sensitive data was limited, and it was protected by its physical isolation and ignorance of its existence. With the digitization of medical data, this information is becoming accessible through distributed systems, including the Internet. This has increased the numbers of people that can potentially access medical information by orders of magnitude, often providing more efficient transfer of medical records and related information. Misu se of a person's medical and genetic data could potentially negatively impact his ability to be hired, and limit his career path and his insurability. Clearly medical information is one of the most sensitive types of information and requires strong security measures. We discuss the requirements and policies required for an access control model suitable for medical and genetic information. We indicate the general structure of such a model and conclude that it requires a layered structure. We then show its highest level. We use the Unified Modeling Language (UML) to model a patient record and we make it more precise by defining constraints using the Object Constraint Language (OCL). .
We discuss an analysis pattern that describes some aspects of a patient treatment instance. Each encounter within a medical facility must be documented. Our pattern describes the breakdown of each treatment instance, or chart into categories for a patient stay or visit in a hospital. Our pattern categorizes this information with a methodology many physicians use to divide their notes, known as SOAP (Subjective, Objective, Assessment, Plan). This pattern is an extension of our previous pattern, the Patient Treatment Records Pattern which describes the collection of treatment instances for each patient within a medical group. The SOAP pattern for medical charts is a categorization of the patient treatment instance.
Analysis patterns seem to be a promising approach supporting software analysis. However, the usefulness of this approach has not been proved. This paper presents a 'big picture' of issues related to application of analysis patterns in software development process from practitioner's perspective. It examines several aspects of analysis patterns and their application in software development. Then, it provides a method of system analysis with analysis patterns. And finally, it presents a case study of analysis with analysis patterns for a system supporting a small real medical centre.
Health Level 7 (HL7), one of the ANSI standards organizations has a mission to provide standards for the execution, management, and integration of data to support clinical patient care. HL7 will play an important role in the implementation of the HIPAA regulations. HL7 has developed a Reference Information Model (RIM), an object-oriented model of clinical data. JAHIS is a Japanese organization that has developed extensions to this RIM. Instead of using the Unified Modeling Language (UML), the standard notation for object-oriented software development, these two organizations have developed specialized object-oriented models. This has resulted in languages which are incompatible with the current use of UML. The consequences of this choice are the loss of the possible use of a large variety of existing models and patterns. What is worse, it will be difficult to add security specifications in their models, a critical aspect in the electronic interchange of medical records. We discuss here the shortcomings of HL7 and JAHIS as modeling languages and as languages in which to add security specifications. We also propose some solutions to this situation.
The paper presents the architecture of a software system managing the patient’s health record and outlines an ontology which is then used as a framework for implementation. The use of this system will help us to realize the full potential of modern, electronic, health care and to optimize this functionality, ontologies are needed. Standards for coded medical terminologies and for a common representation of clinical data will allow patient information to be transmitted clearly and unambiguously between different computers and different software applications in a secure form which is easily searched, interpreted, and manipulated, and thus most useful. We propose architecture to support distributed tasks and data in a health care network. An experimental implementation of the proposed methodology is in work in a small health care network in order to show the usefulness of the proposals as well as their effectiveness in electronic management of patient’s health record.
