PubMed Health⌕ Search

Biomedical subjects

L Alschuler

Publications and source records attributed to L Alschuler.

7 recordsLinked to original sources
PubMed2001

The creation of an ontology of clinical document names.

The efficient use of documents from heterogeneous computer systems is hampered by differences in document-naming practices across organizations. Using an open-consensus method, the Document Ontology Task Force, with support from the Veterans Health Administration, addressed this pervasive problem by developing a clinical document ontology. Based on the analysis of over 2000 clinical document names, the ontology was used to formulate a terminology model which is currently being used to guide the creation of fully-specified document names in LOINC (Logical Observations, Identifiers, Names and Codes). Incorporation into LOINC will enable homogeneous management of documents in a widely distributed environment and will also give rise to a rich polyhierarchy of document names.

Documentation↗
PubMed2000

An update on HL7's XML-based document representation standards.

Many people know of HL7 as an organization that creates healthcare messaging standards. But HL7 is also developing standards for the representation of clinical documents (such as discharge summaries and consultation notes). These document standards comprise the HL7 Clinical Document Architecture (CDA). Last year we presented a high-level conceptual overview of the CDA. Since that time, CDA has entered HL7's formal ballot process (which when successful will make the CDA an ANSI-approved HL7 standard). This article delves into the technical details of the current CDA proposal. Note that due to space limitations, only a subset of CDA details can be described. Also, because the ballot process elicits considerable feedback, it is likely that the material presented here will undergo evolution prior to becoming a final standard. The most up-to-date information is available on HL7's web site (www.hl7.org).

Medical Records Systems, Computerized↗
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↗
PubMed1997

First do no harm: a standard for electronic communication in healthcare.

This paper summarizes recent work on the application of document processing technology, specifically, Standard Generalized Markup Language (SGML) to the problems of electronic exchange of healthcare related information. It includes a short description of the HL7 SGML SIG and current work on SGML standards for healthcare information exchange.

Computer Communication Networks↗
PubMed1997

SGML as a message interchange format in healthcare.

INTRODUCTION: In 1993, The European Committee for Standardization (CEN) studied several syntaxes for interchange formats in healthcare, but excluded SGML due to resource constraints. We sought to extend the CEN report and formally evaluate the use of SGML as a message interchange format. METHODS: We followed the methodology set forth by CEN, using their example scenarios and healthcare data model. General message descriptions based on this model set the functional requirements for the interchange format. These general requirements are then mapped into SGML to see how well they can be supported. RESULTS: Results follow the CEN format, enabling a direct comparison of SGML with ASN.1, ASTM E1238, EDIFACT, EUCLIDES, and ODA (those syntaxes studied by CEN). CONCLUSION: SGML compares favorably with other syntaxes investigated by CEN. None of the interchange formats support all functional requirements. Optimal and standard mechanisms of combining different formats through a modular approach to achieve greater overall functionality requires further study.

Computer Communication Networks↗
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↗