ASTM E2210-02
(Specification)Standard Specification for Guideline Elements Model (GEM)-Document Model for Clinical Practice Guidelines
Standard Specification for Guideline Elements Model (GEM)-Document Model for Clinical Practice Guidelines
SCOPE
1.1 This specification covers a document type definition (DTD) that specifies a standard representation for storing and organizing the heterogeneous information contained in clinical practice guidelines. This specification is intended to facilitate translation of natural-language guideline documents into a format that can be processed by computers. It can be used to represent document content throughout the entire guideline life cycle. Information at both high and low levels of abstraction can be accommodated. This specification is based on the guideline elements model (GEM) created at the Yale Center for Medical Informatics and designed to serve as a comprehensive XML-based guideline document representation.
1.2 This specification refers to and makes use of recommendations from the World Wide Web consortium, the W3C.
1.3 Standard Guideline —DTDThis specification defines a standard DTD for clinical practice guidelines. The DTD is included in Annex A1.
1.4 This standard does not purport to address all of the safety concerns, if any, associated with its use. It is the responsibility of the user of this standard to establish appropriate safety and health practices and determine the applicability of regulatory requirements prior to use.
General Information
Relations
Standards Content (Sample)
NOTICE: This standard has either been superseded and replaced by a new version or withdrawn.
Contact ASTM International (www.astm.org) for the latest information
An American National Standard
Designation: E 2210 – 02
Standard Specification for
Guideline Elements Model (GEM)—Document Model for
Clinical Practice Guidelines
This standard is issued under the fixed designation E 2210; the number immediately following the designation indicates the year of
original adoption or, in the case of revision, the year of last revision. A number in parentheses indicates the year of last reapproval. A
superscript epsilon (e) indicates an editorial change since the last revision or reapproval.
1. Scope E 2183 Guide for XML DTD Design, Architecture and
Implementation
1.1 This specification covers a document type definition
2.2 W3C World Wide Web Consortium:
(DTD) that specifies a standard representation for storing and
XML 1.0 Recommendation
organizing the heterogeneous information contained in clinical
XHTML Basic Recommendation
practice guidelines. This specification is intended to facilitate
XLINK
translation of natural-language guideline documents into a
Namespaces Recommendation
format that can be processed by computers. It can be used to
XSL/XSLT
represent document content throughout the entire guideline life
Schemas
cycle. Information at both high and low levels of abstraction
2.3 HL7 Standards:
can be accommodated. This specification is based on the
Informative Document: Using XML as anAlternative Mes-
guidelineelementsmodel(GEM)createdattheYaleCenterfor
sage Syntax for HL7, Version 2.3.x
Medical Informatics and designed to serve as a comprehensive
Clinical Document Architecture
XML-based guideline document representation.
1.2 Thisspecificationreferstoandmakesuseofrecommen-
3. Terminology
dations from the World Wide Web consortium, the W3C.
3.1 Definitions:
1.3 Standard Guideline DTD—This specification defines a
3.1.1 document type definition (DTD)—the formal defini-
standard DTD for clinical practice guidelines. The DTD is
tion of the elements, structures, and rules for enabling
included in Annex A1.
platform-independent data access via XML, or for marking up
1.4 This standard does not purport to address all of the
a given type of SGML document.
safety concerns, if any, associated with its use. It is the
3.1.2 extensible markup language (XML)—standard from
responsibility of the user of this standard to establish appro-
the World Wide Web Consortium (W3C) that provides for
priate safety and health practices and determine the applica-
tagging of information content within documents, offering a
bility of regulatory requirements prior to use.
means of representation of content in a format that is both
2. Referenced Documents human and machine readable.Through the use of customizable
style sheets and schemas, information can be represented in a
2.1 ASTM Standards:
uniform way, allowing for interchange of both content (data)
E 1239 Guide for Description of Reservation/Registration-
and format (metadata).
Admission, Discharge, Transfer (R-ADT) Systems for
3.1.3 health level 7 (HL7)—a standards organization tradi-
Automated Patient Care Information Systems
tionally focused on standards for healthcare information inter-
E 1384 Guide for Content and Structure of the Electronic
change. HL7 messages are the dominant standard for peer-to-
Health Record (EHR)
peer exchange of clinical text-based information. More
E 1633 Specification for Coded Values Used in the Elec-
recently, HL7 has developed a comprehensive object model of
tronic Health Record
E 2182 Specification for Clinical XML DTDs in Health-
care
http://www.w3.org/XML/
1 5
This specification is under the jurisdiction of ASTM Committee E31 on http://www.w3.org/TR/2000/REC-xhtml-basic-20001219
Healthcare Informatics and is the direct responsibility of Subcommittee E31.35 on http://www.w3.org/XML/Linking
Healthcare Data Analysis. http://www.w3.org/TR/REC-xml-names/
Current edition approved May 10, 2002. Published August 2002. http://www.w3.org/Style/XSL/
2 9
http://www.w3.org http://www.w3.org/XML/Schema
3 10
Annual Book of ASTM Standards, Vol 14.01. http://www.HL7.org
Copyright © ASTM International, 100 Barr Harbor Drive, PO Box C700, West Conshohocken, PA 19428-2959, United States.
E2210–02
the healthcare enterprise and the first level of an XML clinical and tools) to lead the Web to its full potential as a forum for
document architecture. information, commerce, communication, and collective under-
3.1.4 HL7 clinical document architecture (CDA)—a docu- standing.
ment markup standard for the structure and semantics of 3.1.13 XHTML—HTML documents that are well formed
exchanged clinical documents. A clinical document is a docu- and can be processed by an XML parser.
mentation of observations and other services with the follow- 3.1.14 XLL/XLINK/XPOINTER—XLL, the extensible link-
ing characteristics: persistence, stewardship, potential for au- ing language, is divided into two parts, XLinks and XPointers.
thentication, wholeness, and human readability. A CDA XLink, the XML linking language, defines how one document
documentisadefinedandcompleteinformationobjectthatcan links to another document. XPointer, the XML pointer lan-
exist outside of a message and can include text, sounds, and guage, defines how individual parts of a document are ad-
other multimedia content. dressed. XLinks point to a URI (in practice, a URL) that
3.1.5 hypertext markup language (HTML)—the language specifies a particular resource. The URL may include an
used in creating a web page. Its origin is an implementation of XPointer part that more specifically identifies the desired part
SGML DTD. It provides tags regarding the way a document or section of the targeted resource or document. XPointer, the
should be displayed in the text of an HTML document, which XML pointer language, defines an addressing scheme for
act as commands that a browser interprets when downloading individual parts of an XML document. XLinks point to a URI
an HTML file. (in practice, a URL) that specifies a particular resource. The
3.1.6 namespaces—provide a simple method for qualifying URI may include an XPointer part that more specifically
element and attribute names used in XML documents. This is identifies the desired part or element of the targeted resource or
accomplished by associating a particular tag set by associating document. XPointers use the same XPath syntax as XSL
a prefix with a URI reference. XML namespaces provides a transformationstoidentifythepartsofthedocumenttheypoint
mechanism for authoring compound documents (documents to, along with a few additional pieces.
consisting of elements and attributes from multiple DTDs or 3.2 Definitions of Terms Specific to This Standard:
schemas) in such a way that will provide global identification 3.2.1 clinical practice guidelines—systematically devel-
without collisions of names that are the same but are used oped statements to assist practitioner and patient decisions
differently. about appropriate healthcare for specific clinical circum-
3.1.7 parser—a specialized software program that recog- stances.
nizes markup in a document and differentiates the content from 3.2.2 guideline elements model (GEM)—an XML-based
the markup.Aparser that reads a DTD and checks and reports guideline document model that promotes translation of natural
on markup errors is a validating XML parser. A parser can be language guideline documents into a format that can be
built into an XML editor to prevent incorrect tagging and to processed by computers. Developed at the Yale Center for
check whether a document contains all the required elements. Medical Informatics, GEM serves as the basis for this speci-
3.1.8 schema—defines the elements that can appear within fication.
the document and the attributes that can be associated with an 3.2.3 guidelines interchange format (GLIF)—a proposed
element. It also defines the structure of the document: which representation for guideline logic created by the INTERMED
elements are child elements of others, the sequence in which Collaboratory.
the child elements can appear, and the number of child 3.2.4 national guidelines clearinghouse (NGC)—a website
elements.Itdefineswhetheranelementisemptyorcaninclude sponsored by the U.S. Agency for Healthcare Quality and
text. The schema can also define default values for attributes. Researchthatdisseminatesinformationaboutqualifyingguide-
Schema is a W3C term for the next generation of DTDs. lines. It includes a structured vocabulary for describing several
3.1.9 stylesheet—the XSL transformations (XSLT) de- aspects of guidelines.
scribes a vocabulary recognized by an XSLT processor to 3.3 GEM Definitions:
transform information from an organization in the source file 3.3.1 See Table A1.1 in Annex A1.
into a different organization suitable for continued downstream
4. Significance and Use
processing. The extensible stylesheet language (XSL) de-
scribes a vocabulary recognized by a rendering agent to reify 4.1 GEM Representation—The guideline elements model
abstract expressions of format into a particular medium of (GEM) was created to unify representations created by health
presentation. services researchers and by informatics specialists. Specifica-
3.1.10 valid XML document—a document that is well- tion E 2210 DTD is based on the GEM knowledge represen-
formed, with internal or DOCTYPE reference to element tation. It is intended to be:
definition of tags within the document.
3.1.11 well-formed XML document—an XML document
Guidelines for Clinical Practice: From Development to Use, Institute of
that conforms to the syntax as specified by the W3C XML 1.0
Medicine, National Academy Press, Washington, DC, 1992.
recommendation.
http://ycmi.med.yale.edu
3.1.12 World Wide Web Consortium (W3C)—develops in-
http://www.glif.org.
teroperable technologies (specifications, guidelines, software, http://www.guideline.gov
E2210–02
4.1.1 Comprehensive, that is, capable of expressing all the contain content or serve as XLinks to external content. Addi-
knowledge contained in a guideline. Existing health services tionally the DTD may make use of namespaces to resolve
models of guidelines are inadequate for expressing the com- conflicts with other XML standards and XHTML tags.
plexity of knowledge components in sufficient detail to facili-
5.2 GEM Architecture—The root level of this Specification
tate electronic translations. On the other hand, existing infor-
E 2210 DTD is the guideline document. At the next tier, the
matics models are insufficient to model constructs that express
model defines header and body elements. The
and support guideline validity. Lack of confidence in the
.header> includes identity and developer elements. The
validity of guideline recommendations may ultimately limit
includes purpose, ,
end user adherence.
, ,
4.1.2 Expressively adequate to express the complexities and
.components>, testing, and revision elements. Each of these
nuances of clinical medicine while remaining informationally
elements comprises one or more additional levels of guideline
equivalent to the original guideline. Most tagged elements in
constructs.
the Specification E 2210 DTD store the actual language of the
5.3 Elements—Elements can appear as often as required.
guideline, thereby remaining true to the original. Moreover,
Most elements store information that is literally presented in
this DTD does not require recommendation knowledge to be
the guideline text itself, for example, release date, name of
structured in a temporal sequence, an often artificial transfor-
sponsoring organization, and recommendation text. A small
mation necessary for algorithmic representations.
number of metalevel tags provide information about the
4.1.3 Flexible, that is, a useful model must be able to deal
guideline that has been interpreted, for example,
with the variety and complexity of guidelines. The representa-
.type>. To distinguish whether an element’s content is explic-
tion should permit modeling at high and low levels of
itlystatedwithintheguidelinedocumentorwasinferredbythe
granularity so that guidelines can be interpreted at different
person who performed the markup, each element has an
levels of abstraction. The Specification E 2210 DTD allows
attribute called “source.” The source attribute can take values
markupusinghigh-leveltagsordeeperanalysisusingelements
of “explicit,” “inferred,” or in some cases “NGC” (to indicate
from lower levels in the hierarchy. In addition, the open XML
that the National Guidelines Clearinghouse structured vocabu-
document model can be modified easily if necessary to
lary is used).
accommodate missing semantic constructs.
5.4 Identity—Information that identifies a particular guide-
4.1.4 Comprehensible, that is, it should match the stake-
line document and describes it in general terms is clustered
holders’ normal problem-solving language and allow domain
within this construct. The identity element includes the guide-
experts to describe their knowledge with little effort. The
line’s complete title, a citation that references its publication,
Specification E 2210 DTD markup does not require knowledge
its , its availability (in electronic and print
of programming. The markup process parallels physical high-
formats) and a person or organization to be contacted for
lighting of a document and should be learned easily by
further information. The status element indicates whether the
nonprogrammers.
guideline has been updated or revised. Since many current
4.1.5 Shareable across institutions. The use of XML for
guidelines are released as packages that may include patient
knowledge representation and markup provides unparalleled
educationmaterials,foreignlanguageversions,quickreference
cross-platform compatibility.
guides, and technical reports, a construct for
4.1.6 Reusable across all phases of the guideline life cycle.
.document> is included. An entry stored in the adaptation
4.2 Conformance—A document is tested for conformance
element identifies whether the guideline has been adapted from
to this specification by a validating XML parser according to
another publication.
theW3CXML1.0recommendation. Aconformantdocument
5.5 Developer—The organization responsible for develop-
mustvalidatewithouteitherwell-formednessorvalidityerrors,
ment of the guideline is identified and described. A
according to XML 1.0. A conformant document must also
er.type> element (for example, medical specialty society,
conform to constraints expressed within the prose of this
federal government agency, managed care organization) pro-
specification; however, this specification does not expr
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.