
Keith W. BooneAudacious Inquiry · Government Contracting
Keith W. Boone
Master of Biomedical Informatics
About
33
Publications
3,973
Reads
How we measure 'reads'
A 'read' is counted each time someone views a publication summary (such as the title, abstract, and list of authors), clicks on a figure, or views or downloads the full-text. Learn more
105
Citations
Publications
Publications (33)
Objective
There is little readily available data about the size and characteristics of the healthcare information technology workforce. We sought to update a previous description of the size, growth, and characteristics of this workforce based on the Healthcare Information Management Systems Society (HIMSS) Analytics® Database, a resource that incl...
This second version of the mHIMSS Roadmap was developed by dedicated and knowledgeable contributors in the field of mobile health technology, part of HIMSS mHealth Community. While the first version was designed as a strategic framework to healthcare stakeholders to develop and implement a mobile strategy, this second version builds on the precedin...
The CDATM standard uses Extensible Markup Language (XML) [1] to represent information. XML looks very similar to HTML, but is actually
a lower level standard upon which other markup languages are built. XHTML is actually a reformulation of HTML into the XML
syntax.
Pediatric palliative care currently faces many challenges including unnecessary pain from insufficiently personalized treatment, doctor-patient communication breakdowns, and a paucity of usable patient-centric information. Recent advances in informatics for consumer health through eHealth initiatives have the potential to bridge known communication...
The CDA contains the original Clinical Statement model used in HL7. The clinical statement model as defined in the CDA standard
went on to become a standard of its own in HL7, and is now the foundation of other standards in HL7. As a result, understanding
the clinical statement model in CDA can help you understand many other HL7 Version 3 standard...
The CDA™ standard builds upon the HL7 Version 3 stack of standards. In the lowest layer of that stack are standards on vocabulary
and data types. On top of those is the HL7 Reference Information Model.
At least two open source APIs exist to read CDA clinical documents into an object model in memory. The general pattern is
to create a Clinical Document object in memory, initialize it from a CDA document, and then begin to access the components
of the model using various setter and getter methods. The CDAPI from Mirth Corporation is one open source...
A very common way to generate CDA documents is by converting an HL7 Version 2 message into the CDA format. The MDM, ORU and
ADT messages are the most common ones that are converted to CDA.
The CDA body represents the narrative content of the clinical document. The body is simply a part of the clinical document,
and is accessed through the component association class.
According to §1.1 of the HL7 Templates DSTU:
A template is an expression of a set of constraints on the RIM or a RIM derived model that is used to apply additional constraints
to a portion of an instance of data which is expressed in terms of some other Static Model. Templates are used to further
define and refine these existing models to specify...
The binary data type is a collection of raw bits. HL7 treats this conceptually as a list of BooleanNonNull values. An empty
stream of binary data is considered to be an exceptional (null) value. The binary data type is an abstract one, which means
that this data type is cannot be used inside a CDATM document. To send binary data see Encapsulated Da...
All of the HL7 Version 3 data types derive their properties from the ANY data type. Common features of all of the data types
are implemented here. For example, almost all HL7 data types can indicate that the value is unknown. This property is implemented
in the CDATM schema through the ANY data type.
The CDA header is the first part of the CDA Document. It includes all content up to the element that contains the body of the document.
The CDATM standard describes the structure of a clinical document using an HL7 modeling drawing that is based on UML as explained above.
A miniature of that diagram appears below. This diagram is called the CDA R-MIM. In HL7 Version 3, the term R-MIM stands for
restricted message information model.
The HL7 Reference Information Model (or RIM for short) is the UML model for healthcare information from which the CDATM Standard
is derived. A simplified diagram of the RIM appears in the figure below (the smaller classes are not used in CDA). This diagram
shows that the RIM has six base classes from which all other HL7 classes are derived.
This chapter appears before the introduction of the various data types used to support coding because of the importance of
codes in the CDATM (and HL7 Version 3 standards in general).
Vocabulary is an important component in the HL7 Reference Information Model. The HL7 Version 3 Reference Information Model
is often described as a language for com...
Validation is the process of ensuring that something conforms to the requirements for it. In the context of XML, an XML document
is valid if it conforms to the schema defined for it. The most commonly used schema these days is the W3C XML Schema standard.
The CDA standard provides a schema using the W3C XML Schema standard that can be used for val...
The HL7 Clinical Document Architecture is a standard XML format for clinical documents. This standard is based upon the HL7 Version 3 Reference Information Model (RIM), Data types and Vocabulary standards. The CDATM standard is also recognized as an ISO and ANSI standard.
The HL7 Abstract Data Types specification includes several types of abstract collections of different data types, including bags, sets and lists. These collection data types can be used with any of the other simpler data types. Unlike other object models, the HL7 collection types do not derive sets or lists from the bag collection type, even though...
There are numerous implementation guides on CDA that have been developed around the world. The first CDA Release 2.0 implementation guide was published by in 2004 even before CDA Release 2.0 became an HL7 standard in 2005. Approximately 10% of the HL7 ballots over the last five years have been for CDA implementation guides. Since CDA Release 2.0 wa...
Clinical documentation is used throughout healthcare to describe care provided to a patient, communicate essential information between healthcare providers and to maintain a patient medical record. What is a clinical document? The simple and easy answer is that a clinical document is anything that you might find in a patient’s medical record or any...
HL7 Version 3 allows you to say “every Tuesday for 10 minutes before 10:00 am, and Thursday 10 minutes before 2:00 pm between Labor Day and Memorial Day with the exception of holidays” as a structured set of dates. This by the way, is a dosing regimen for a treatment I used swimmers ear when swimming lessons ended at 10 am Tuesday and 2 pm Thursday...
CDATM provides eight different data types to record what is commonly thought of as demographic data. These are address parts and addresses; name parts; organization, personal and other names; identifiers, and telecommunications endpoints.
Codes represent distinct concepts in a coding system, also called a terminology or vocabulary. All coded representations in HL7 derive from the Concept Descriptor (CD) data type described in more detail below.
This presentation will review lessons learned in implementing standards-based alert messages within the GE Centricity EMR product. It will start with a brief overview discussing the standards that have been selected by ANSI/HITSP for communicating alerts. The rationale for selecting HITSP T81 for the proof of concept will be given. During the selec...
This article provides guidelines for HIM Professionals in the development of a data dictionary to use with EHR and other HIT systems.
HIM professionals have an opportunity to take advantage of the global pressure to implement EHRs. HIM professionals can facilitate decisions regarding the content of the EHR based on internal and external needs and existing standards. While we await the outcome of standards harmonization efforts at the federal level, it’s not too early to advocate...