09.11.2012 Views

Pediatric Informatics: Computer Applications in Child Health (Health ...

Pediatric Informatics: Computer Applications in Child Health (Health ...

Pediatric Informatics: Computer Applications in Child Health (Health ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

416 S.T. Rosenbloom and J. Kuhl<br />

the physician will be able to make decisions and prescribe the necessary therapies<br />

more efficiently.<br />

Standards are pr<strong>in</strong>ciples and rules designed to ensure that methods used and<br />

products created reliably and consistently conform to expectations. Software<br />

standards <strong>in</strong> particular exist to align the structure and data conta<strong>in</strong>ed <strong>in</strong> disparate<br />

computer systems and application programs. 7 Typically, such standards detail<br />

the m<strong>in</strong>imum set of functions that the software provides, the methods used to<br />

achieve those functions, and the formatt<strong>in</strong>g of the data structure. The goal of<br />

standards is to ensure that both data and users’ experiences are similar from<br />

one computer system to another, and that <strong>in</strong>formation can flow easily between<br />

computer systems. 7–9 Standards for EHR systems and cl<strong>in</strong>ical data may <strong>in</strong>clude<br />

specifications for the terms used to represent medical entities and the relationships<br />

between entities and <strong>in</strong>dividual patients. For example, medication standards may<br />

<strong>in</strong>clude details about what words and spell<strong>in</strong>gs to be used to represent each medication,<br />

<strong>in</strong>gredient, dos<strong>in</strong>g frequency and dose form, as well as the data structure<br />

that l<strong>in</strong>ks a given medication to the dates that it was started or refilled and to the<br />

patient who is tak<strong>in</strong>g it.<br />

Standards for cl<strong>in</strong>ical data exist with the primary objective of enabl<strong>in</strong>g it to<br />

be aggregated, shared, and exchanged with<strong>in</strong> and among various EHR systems. 8,9<br />

The ability for data to be shared among computer systems without loss of detail<br />

or mean<strong>in</strong>g is termed “<strong>in</strong>teroperability.” For data to be maximally <strong>in</strong>teroperable, it<br />

must be normalized to a s<strong>in</strong>gle form and content. This s<strong>in</strong>gle form and content is<br />

a standard.<br />

32.2 Types of Cl<strong>in</strong>ical Data Standards<br />

Data standards designed to support aggregation and exchange generally consist of<br />

three components, each of which may be def<strong>in</strong>ed us<strong>in</strong>g a term<strong>in</strong>ology or a guidel<strong>in</strong>e:<br />

(1) the scope and content of the standard; (2) the syntax and formatt<strong>in</strong>g of the<br />

content; and (3) the actual semantics and words used to represent the content. We<br />

will consider each of these types of standards.<br />

32.2.1 Content, Function, and Quality Standards<br />

One major purpose of software standards for EHR systems is to def<strong>in</strong>e the core<br />

set of functions, features, and activities that such systems should support. Def<strong>in</strong><strong>in</strong>g<br />

necessary functions, with descriptions of each, ensures that system developers,<br />

evaluators, and users all have similar expectations of what EHR systems do (and do<br />

not do). A list<strong>in</strong>g of desired functions, features, and activities serves as a standard<br />

for content or quality, because it def<strong>in</strong>es the m<strong>in</strong>imum set of content that a piece of<br />

software should provide, and aga<strong>in</strong>st which its quality can be judged.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!