Robert H. Dolin
Current Organizations / Institutes
The organizations/institutes from the scholar's latest article
Research Subjects
Research Interests
Robert H. Dolin has a total of 38 co-authors. Here are the top co-authors by number of shared publications:
L Alschuler
4 shared publicationsCalvin Beebe
Affiliations of the authors: Kaiser Permanente, Pasadena, CA (RHD, PVB); Alschuler Associates, LLC, East Thetford, VT (LA); Consultant, Laguna Beach, CA (SB); Mayo Clinic, Rochester, MN (CB); LAI Technology, Homewood, IL (FMB); Amnon Shabo (Shvo), IBM Haifa Research Lab, Haifa, Israel (AS)
2 shared publicationsJ E Mattison
2 shared publicationsLiora Alschuler
Affiliations of the authors: Kaiser Permanente, Pasadena, CA (RHD, PVB); Alschuler Associates, LLC, East Thetford, VT (LA); Consultant, Laguna Beach, CA (SB); Mayo Clinic, Rochester, MN (CB); LAI Technology, Homewood, IL (FMB); Amnon Shabo (Shvo), IBM Haifa Research Lab, Haifa, Israel (AS)
2 shared publicationsPaul V. Biron
Affiliations of the authors: Kaiser Permanente, Pasadena, CA (RHD, PVB); Alschuler Associates, LLC, East Thetford, VT (LA); Consultant, Laguna Beach, CA (SB); Mayo Clinic, Rochester, MN (CB); LAI Technology, Homewood, IL (FMB); Amnon Shabo (Shvo), IBM Haifa Research Lab, Haifa, Israel (AS)
2 shared publicationsA Abilla
1 shared publication
Latest Publications
- 11 October 2007
- Vol. 2007, 186-90
Enabling joint commission medication reconciliation objectives with the HL7 / ASTM Continuity of Care Document standard.
We sought to determine how well the HL7/ASTM Continuity of Care Document (CCD) standard supports the requirements underlying the Joint Commission medication reconciliation recommendations. In particular, the Joint Commission emphasizes that transition points in the continuum of care are vulnerable to communication breakdowns, and that these breakdowns are a common source of medication errors. These transition points are the focus of communication standards, suggesting that CCD can support and enable medication related patient safety initiatives. Data elements needed to support the Joint Commission recommendations were identified and mapped to CCD, and a detailed clinical scenario was constructed. The mapping identified minor gaps, and identified fields present in CCD not specifically identified by Joint Commission, but useful nonetheless when managing medications across transitions of care, suggesting that a closer collaboration between the Joint Commission and standards organizations will be mutually beneficial. The nationally recognized CCD specification provides a standards-based solution for enabling Joint Commission medication reconciliation objectives.
- 11 October 2007
- Vol. 2007, 186-90
Enabling joint commission medication reconciliation objectives with the HL7 / ASTM Continuity of Care Document standard.
We sought to determine how well the HL7/ASTM Continuity of Care Document (CCD) standard supports the requirements underlying the Joint Commission medication reconciliation recommendations. In particular, the Joint Commission emphasizes that transition points in the continuum of care are vulnerable to communication breakdowns, and that these breakdowns are a common source of medication errors. These transition points are the focus of communication standards, suggesting that CCD can support and enable medication related patient safety initiatives. Data elements needed to support the Joint Commission recommendations were identified and mapped to CCD, and a detailed clinical scenario was constructed. The mapping identified minor gaps, and identified fields present in CCD not specifically identified by Joint Commission, but useful nonetheless when managing medications across transitions of care, suggesting that a closer collaboration between the Joint Commission and standards organizations will be mutually beneficial. The nationally recognized CCD specification provides a standards-based solution for enabling Joint Commission medication reconciliation objectives.
- Top Cited PapersOpen Access
- 1 January 2006
- Published by Oxford University Press (OUP) in Journal of the American Medical Informatics Association
- Vol. 13 (1) , 30-39
HL7 Clinical Document Architecture, Release 2
Clinical Document Architecture, Release One (CDA R1), became an American National Standards Institute (ANSI)–approved HL7 Standard in November 2000,
- 1 January 2006
- Published by Oxford University Press (OUP) in Journal of the American Medical Informatics Association
- Vol. 13 (1) , 30-39
Top Cited PapersOpen AccessHL7 Clinical Document Architecture, Release 2
Clinical Document Architecture, Release One (CDA R1), became an American National Standards Institute (ANSI)–approved HL7 Standard in November 2000,
- Top Cited PapersOpen Access
- 1 November 2001
- Published by Oxford University Press (OUP) in Journal of the American Medical Informatics Association
- Vol. 8 (6) , 552-569
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
- 1 November 2001
- Published by Oxford University Press (OUP) in Journal of the American Medical Informatics Association
- Vol. 8 (6) , 552-569
Top Cited PapersOpen AccessThe 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
- 1 January 2001
- Vol. 84, 94-8
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.
- 1 January 2001
- Vol. 84, 94-8
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.
- 1 January 2001
- p. 139-43
The SNOMED RT Procedure Model.
SNOMED RT represents a fundamental change from prior versions of SNOMED. The logic-based structure of SNOMED RT enables concepts to be defined more explicitly, providing an opportunity to address inconsistencies and ambiguities present in prior SNOMED concept definitions. Create a unifying organizational strategy for all SNOMED RT procedures, and remove ambiguities in procedure concept definitions. A comprehensive model of procedures was developed, based on a set of guiding principles and a review of known existing models. All SNOMED RT procedures are categorized by a common set of "root procedures" (high level atomic actions), and are more explicitly defined by a shared set of defining relationships. While the objectives have largely been met, open issues continue to be addressed. The similarity between procedure models of SNOMED RT and the U.K. s Clinical Terms Version 3 is proving to greatly facilitate the full integration of the two terminologies into a merged vocabulary to be known as SNOMED Clinical Terms (SNOMED CT), slated to be released in the near future.
- 1 January 2001
- p. 139-43
The SNOMED RT Procedure Model.
SNOMED RT represents a fundamental change from prior versions of SNOMED. The logic-based structure of SNOMED RT enables concepts to be defined more explicitly, providing an opportunity to address inconsistencies and ambiguities present in prior SNOMED concept definitions. Create a unifying organizational strategy for all SNOMED RT procedures, and remove ambiguities in procedure concept definitions. A comprehensive model of procedures was developed, based on a set of guiding principles and a review of known existing models. All SNOMED RT procedures are categorized by a common set of "root procedures" (high level atomic actions), and are more explicitly defined by a shared set of defining relationships. While the objectives have largely been met, open issues continue to be addressed. The similarity between procedure models of SNOMED RT and the U.K. s Clinical Terms Version 3 is proving to greatly facilitate the full integration of the two terminologies into a merged vocabulary to be known as SNOMED Clinical Terms (SNOMED CT), slated to be released in the near future.
- 1 January 2000
- p. 190-4
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).
- 1 January 2000
- p. 190-4
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).
- 22 June 1999
- Vol. 16 (2) , 60-4
Clinical practice guidelines on the Internet. A structured, scalable approach.
- 22 June 1999
- Vol. 16 (2) , 60-4
Clinical practice guidelines on the Internet. A structured, scalable approach.
- Open Access
- 1 March 1998
- Published by Oxford University Press (OUP) in Journal of the American Medical Informatics Association
- Vol. 5 (2) , 203-213
Evaluation of a "Lexically Assign, Logically Refine" Strategy for Semi-automated Integration of Overlapping Terminologies
Objective: To evaluate a “lexically assign, logically refine” (LALR) strategy for merging overlapping healthcare terminologies. This strategy combines
- 1 March 1998
- Published by Oxford University Press (OUP) in Journal of the American Medical Informatics Association
- Vol. 5 (2) , 203-213
Open AccessEvaluation of a "Lexically Assign, Logically Refine" Strategy for Semi-automated Integration of Overlapping Terminologies
Objective: To evaluate a “lexically assign, logically refine” (LALR) strategy for merging overlapping healthcare terminologies. This strategy combines
- 1 January 1997
- p. 635-9
SGML as a message interchange format in healthcare.
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. 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 follow the CEN format, enabling a direct comparison of SGML with ASN.1, ASTM E1238, EDIFACT, EUCLIDES, and ODA (those syntaxes studied by CEN). 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.
- 1 January 1997
- p. 635-9
SGML as a message interchange format in healthcare.
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. 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 follow the CEN format, enabling a direct comparison of SGML with ASN.1, ASTM E1238, EDIFACT, EUCLIDES, and ODA (those syntaxes studied by CEN). 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.