PubMed Health⌕ Search

Biomedical subjects

D Essin

Publications and source records attributed to D Essin.

5 recordsLinked to original sources
PubMed1999

HL7 document patient record architecture: an XML document architecture based on a shared information model.

The HL7 SGML/XML Special Interest Group is developing the HL7 Document Patient Record Architecture. This draft proposal strives to create a common data architecture for the interoperability of healthcare documents. Key components are that it is under the umbrella of HL7 standards, it is specified in Extensible Markup Language, the semantics are drawn from the HL7 Reference Information Model, and the document specifications form an architecture that, in aggregate, define the semantics and structural constraints necessary for the exchange of clinical documents. The proposal is a work in progress and has not yet been submitted to HL7's formal balloting process.

Humans↗
PubMedDate not supplied

The HL7 Clinical Document Architecture.

Many people know of Health Level 7 (HL7) as an organization that creates health care messaging standards. Health Level 7 is also developing standards for the representation of clinical documents (such as discharge summaries and progress notes). These document standards make up the HL7 Clinical Document Architecture (CDA). The HL7 CDA Framework, release 1.0, became an ANSI-approved HL7 standard in November 2000. This article presents the approach and objectives of the CDA, along with a technical overview of the standard. The CDA is a document markup standard that specifies the structure and semantics of clinical documents. A CDA document is a defined and complete information object that can include text, images, sounds, and other multimedia content. The document can be sent inside an HL7 message and can exist independently, outside a transferring message. The first release of the standard has attempted to fill an important gap by addressing common and largely narrative clinical notes. It deliberately leaves out certain advanced and complex semantics, both to foster broad implementation and to give time for these complex semantics to be fleshed out within HL7. Being a part of the emerging HL7 version 3 family of standards, the CDA derives its semantic content from the shared HL7 Reference Information Model and is implemented in Extensible Markup Language. The HL7 mission is to develop standards that enable semantic interoperability across all platforms. The HL7 version 3 family of standards, including the CDA, are moving us closer to the realization of this vision.

Computer Communication Networks↗
PubMedDate not supplied

Information technology, health care, and the future: what are the implications for the clinical laboratory?

As new information systems are offered for the clinical laboratory, advanced applications and improvements in computer hardware continue to dominate marketing presentations and fascinate the decision maker. However, the most important issue for all of our clinical information systems is not the speed of the hardware, the reliability of the systems software, or the ability of applications to carry out routine tasks in some novel or elegant manner. Rather, it is "coping"--the ability of a system to manage new issues that arise as information requirements change over time and to manage all the unexpected events that occur in the course of regular work but that do not follow the usual sequence of procedures. The need for new processing conventions to cope with unexpected situations without creating new problems is not unique to health care. The need is present wherever the real world intrudes directly and significantly into critical operations. Moreover, the pressure to adjust to changing external circumstances continues to grow as the rate of change in our information-based society increases. The lack of general coping procedures, although long ignored, has become such a pervasive handicap that marked improvements in this type of flexibility will be introduced over this decade. New software designs that deal with coping issues are already beginning to appear and to bear fruit. When purchasing any new laboratory computer system today, software that demonstrates an effective coping flexibility should be given more weight than fascinating innovations in hardware or software that are the favorites of vendor marketers. It is now possible to test for such flexibility on a site-specific basis.

Clinical Laboratory Information Systems↗