Standard Practice for Defining and Implementing Pharmacotherapy Information Services within the Electronic Health Record (EHR) Environment and Networked Architectures

SCOPE
1.1 This practice applies to the process of defining and documenting the capabilities, logical data sources, and pathways of data exchange regarding pharmacotherapy information services within a given network architecture serving a set of healthcare constituents.
1.2 This practice is not a technical implementation standard but, rather, describes how the implementation methods and techniques can be used to coordinate pharmacotherapy services logically within an electronic health record (EHR) systems environment involving participating organizations and sites connected by a networked communication system.
1.3 This practice covers the content of the nodes and arcs of the resulting logical network involving EHR, pharmacy, and clinical laboratory-capable sites. This practice also considers the various purposes and organizational arrangements for coordinating pharmacotherapy services within the network boundaries and the considerations for connections among external networks.
1.4 This practice refers to other standards for conventions within various data domains, such as pharmacy systems, clinical laboratory information management systems (CLIMS), and EHR systems, and for messaging conventions.
1.5 This practice is intended to outline how integration of pharmacy, CLIMS, and EHR information systems can be undertaken to result in a transparent pharmacotherapy clinical decision support environment, regardless of the underlying implementation architecture, by describing the logical interoperability of information domains as facilitated by information and communications technology (ICT).
1.6 This practice is directed at pharmacists, clinical pharmacologists, clinical laboratorians, information system managers, and information systems vendors for use in planning and implementing coordinated pharmacotherapy services through effective dialog.
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 limitations prior to use.

General Information

Status
Historical
Publication Date
30-Nov-2006
Current Stage
Ref Project

Relations

Buy Standard

Standard
ASTM E2538-06 - Standard Practice for Defining and Implementing Pharmacotherapy Information Services within the Electronic Health Record (EHR) Environment and Networked Architectures
English language
39 pages
sale 15% off
Preview
sale 15% off
Preview

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: E2538 – 06
Standard Practice for
Defining and Implementing Pharmacotherapy Information
Services within the Electronic Health Record (EHR)
Environment and Networked Architectures
This standard is issued under the fixed designation E2538; 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 (´) indicates an editorial change since the last revision or reapproval.
1. Scope 1.7 This standard does not purport to address all of the
safety concerns, if any, associated with its use. It is the
1.1 This practice applies to the process of defining and
responsibility of the user of this standard to establish appro-
documenting the capabilities, logical data sources, and path-
priate safety and health practices and determine the applica-
waysofdataexchangeregardingpharmacotherapyinformation
bility of regulatory limitations prior to use.
services within a given network architecture serving a set of
healthcare constituents.
2. Referenced Documents
1.2 This practice is not a technical implementation standard
2.1 ASTM Standards:
but, rather, describes how the implementation methods and
E1239 PracticeforDescriptionofReservation/Registration-
techniquescanbeusedtocoordinatepharmacotherapyservices
Admission, Discharge, Transfer (R-ADT) Systems for
logically within an electronic health record (EHR) systems
Electronic Health Record (EHR) Systems
environment involving participating organizations and sites
E1340 GuideforRapidPrototypingofInformationSystems
connected by a networked communication system.
E1384 Practice for Content and Structure of the Electronic
1.3 This practice covers the content of the nodes and arcs of
Health Record (EHR)
the resulting logical network involving EHR, pharmacy, and
E1578 Guide for Laboratory Information Management Sys-
clinical laboratory-capable sites. This practice also considers
tems (LIMS)
the various purposes and organizational arrangements for
E1633 Specification for Coded Values Used in the Elec-
coordinating pharmacotherapy services within the network
tronic Health Record
boundaries and the considerations for connections among
E1714 Guide for Properties of a Universal Healthcare
external networks.
Identifier (UHID)
1.4 This practice refers to other standards for conventions
E1715 Practice forAn Object-Oriented Model for Registra-
within various data domains, such as pharmacy systems,
tion, Admitting, Discharge, and Transfer (RADT) Func-
clinicallaboratoryinformationmanagementsystems(CLIMS),
tions in Computer-Based Patient Record Systems
and EHR systems, and for messaging conventions.
E1744 Practice for View of Emergency Medical Care in the
1.5 This practice is intended to outline how integration of
Electronic Health Record
pharmacy, CLIMS, and EHR information systems can be
E1762 Guide for Electronic Authentication of Health Care
undertaken to result in a transparent pharmacotherapy clinical
Information
decision support environment, regardless of the underlying
E1869 Guide for Confidentiality, Privacy,Access, and Data
implementation architecture, by describing the logical interop-
Security Principles for Health Information Including Elec-
erability of information domains as facilitated by information
tronic Health Records
and communications technology (ICT).
E1985 Guide for User Authentication and Authorization
1.6 This practice is directed at pharmacists, clinical phar-
E1986 Guide for Information Access Privileges to Health
macologists, clinical laboratorians, information system manag-
Information
ers, and information systems vendors for use in planning and
implementing coordinated pharmacotherapy services through
effective dialog.
This practice is under the jurisdiction ofASTM Committee E31 on Healthcare
Informatics and is the direct responsibility of Subcommittee E31.25 on Healthcare For referenced ASTM standards, visit the ASTM website, www.astm.org, or
Data Management, Security, Confidentiality, and Privacy. contact ASTM Customer Service at service@astm.org. For Annual Book of ASTM
Current edition approved Dec. 1, 2006. Published January 2007. DOI: 10.1520/ Standards volume information, refer to the standard’s Document Summary page on
E2538-06. the ASTM website.
Copyright © ASTM International, 100 Barr Harbor Drive, PO Box C700, West Conshohocken, PA 19428-2959, United States.
E2538 – 06
E1987 Guide for Individual Rights Regarding Health Infor- ANSI/IEEE 1320.1y 1998 (R2004) Standard for Concep-
mation tual Modeling Language—Syntax and Semantics for
E1988 Guide for Training of Persons who have Access to IDEF0
Health Information ANSI/IEEE 1320.2y 1998 (R2004) Standard for Concep-
E2017 Guide for Amendments to Health Information tual Modeling Language—Syntax and Semantics for
E2066 Guide for Validation of Laboratory Information IDEF1X97 (IDEF Object)
Management Systems
ANSI/IEEE 1362y 1998 Guide for Information
E2084 Specification forAuthentication of Healthcare Infor- Technology—System Definition—Concept of Operations
mation Using Digital Signatures
Document
E2085 Guide on Security Framework for Healthcare Infor- ANSI/IEEE 1490y 2003 IEEE Guide IEEE—Adoption of
mation
PMI Standard—AGuide to Project Management Body of
E2086 Guide for Internet and Intranet Healthcare Security Knowledge, 2000 Edition PMI
E2145 Practice for Information Modeling
ANSI/IEEE 12207.0y 1996 Standard for Information
E2147 Specification forAudit and Disclosure Logs for Use
Technology—Software Life Cycle Processes
in Health Information Systems
ANSI/IEEE 12207.1y 1997 Guide for Information
E2171 Practice for Rating-Scale Measures Relevant to the
Technology—Software Life Cycle Processes—Life Cycle
Electronic Health Record
Data
E2457 Terminology for Healthcare Informatics
ANSI/IEEE 12207.2y 1997 Guide for Information
E2473 Practice for the Occupational/Environmental Health
Technology—Software Life Cycle Processes—
View of the Electronic Health Record
Implementation Considerations
P110 Proposed Guide to Assist in the Defining, Procuring,
2.3 ANSI/HL7 Standards:
Installing, and Implementing of a Computerized Hospital
ANSI/HL7 Interface Standard v2.4, v2.5, v3.0
Pharmacy System
HL7 Message Development Framework v3.3, Dec. 1999
2.2 ANSI/IEEE Standards:
2.4 ANSI/ADA Standards:
ANSI X3.172 American National Dictionary for Informa-
ANSI/ADA TR 1039 2005 Clinical Content Data Model
tion Systems
ANSI/ADA 1000.0 Introduction, Model Architecture, and
ANSI/IEEE 610.12y 1990 (R2002) Standard Glossary of
Specification Framework
Software Engineering Terminology
ANSI/ADA 1000.1 Individual Identification
ANSI/IEEE 830y 1998 Software Requirements Specifica- ANSI/ADA 1000.2 Codes and Nomenclature
tion
ANSI/ADA 1000.3 Individual Characteristics
ANSI/IEEE 1058y 1998 Software Project Management ANSI/ADA 1000.4 Population Characteristics
Plans ANSI/ADA 1000.5 Organization
ANSI/IEEE 1062y 1998 (R2002 includes 1062a) Recom- ANSI/ADA 1000.6 Location
mended Practice for Software Acquisition ANSI/ADA 1000.7 Communication
ANSI/IEEE 1063y 2001 Software User Documentation ANSI/ADA 1000.8 Healthcare Event
ANSI/ADA 1000.9 Health Materiel
ANSI/IEEE 1073y 1996 Framework and Overview
ANSI/ADA 1000.10 Health Services
ANSI/IEEE 1073.3.1y 2001/Amd1-2001 Transport Profile
ANSI/ADA 1000.11 Health Service Resources
(redesignated 11073-3-1, Standard for Medical Device
ANSI/ADA 1000.12 Population Health Facts
Communications-Transport Profile-Connection Mode)
ANSI/ADA 1000.13 Patient Health Facts
ANSI/IEEE 1073.4.1y 2001 Physical Layer-Cable Con-
ANSI/ADA 1000.14 Health Condition Diagnosis
nected (redesignated 11073-4-1, Standard for Medical
ANSI/ADA 1000.15 Health Service Plan
Device Communications—Physical Layer Interface—
ANSI/ADA 1000.16 Patient Health Service
Cable Connection)
ANSI/ADA 1000.17 Clinical Investigation
ANSI/IEEE 1074y 2006 Standard for Developing Life
ANSI/ADA 1000.18 Comments Subject Area
Cycle Processes
2.5 ISO Standards:
ANSI/IEEE 1074.1y 1995 Guide for Developing Life
ISO/IECTR 9789 InformationTechnology—Guidelines for
Cycle Processes
the Organization and Representation of Data Elements for
ANSI/IEEE 1220y 2005 Standard for Application and
Data Interchange-Coding Methods and Principles
Management of the System Engineering Process
ISO 12200 Computer Applications in Terminology—
ANSI/IEEE 1233y 1998 (R2002 includes 1233a) Guide to
Machine-Readable Terminology Interchange Format
Preparing System Requirements Specifications
(MARTIF)—Negotiated Interchange
ISO 12620 Computer Applications in Terminology—Data
Categories
Withdrawn. The last approved version of this historical standard is referenced
ISO IS 12207 Information Technology—Software Life
on www.astm.org.
Cycle Processes
Withdrawn 1988.
ISO IS 15188 Project Management Guidelines for Termi-
Available fromAmerican National Standards Institute (ANSI), 25 W. 43rd St.,
4th Floor, New York, NY 10036, http://www.ansi.org. nology Standardization
E2538 – 06
ISO 15189 Quality Management in the Clinical Laboratory men Tubes in the Clinical Laboratory
ISO DIS 15193 Measurement of Quantities in Samples of
CLSI LIS-8A Guide for Functional Requirements of Clini-
Biologic Origin—Reference Methods
cal Laboratory Information Management Systems
ISO DIS 15194 Measurement of Quantities in Samples of
CLSI LIS-9A Guide for Coordination of Clinical Labora-
Biologic Origin—Reference Materials
tory Services in an Electronic Health Record Environment
ISO 15195 Requirements for Reference Measurement
and Networked Architectures
Laboratories
CLSI POCT1 Point of Care Connectivity
ISO WD 15288 System Life Cycle Processes
DICOM Supplement 15 Visible Light Image, Anatomic
ISO 15440 Guide for Life Cycle Processes
Frame of Reference, Accession and Specimen for Endos-
ISO 17511 Traceability of Calibration and Control Materi-
copy, Microscopy, and Photography
als
EIA/IEEE J-Std-016 Standard for Information Technology,
2.6 Other Standards:
Software Life Cycle Processes, Software Development,
AAMI SW68:2001 Medical Device Software-Software Life 10
Acquirer-Supplier Agreement
Cycle Processes
IUPAC/IFCC Silver Book: Compendium of Terminology
ANSI X12
and Nomenclature of Properties in Clinical Laboratory
CEN ENV 1613 Medical Informatics—Messages for the
Sciences
exchange of laboratory information
IUPAC/IFCC Properties and Units in Clinical Laboratory
CEN ENV 1614 Healthcare Informatics—Structure for no-
Sciences X Properties and Units in General Clinical
menclature, classification and coding of properties in
Chemistry
clinical laboratory sciences
IUPAC/IFCC Properties and Units in Clinical Laboratory
CEN EN 12017 Medical Informatics Vocabulary (MIVoc)
Sciences XII Properties and Units in Clinical Pharmacol-
CEN EN 12264 Categorical Structures of Systems of
ogy and Toxicology
Concepts—Model for Representation of Semantics
NCPDP SCRIPT v9.0
(MOSE)
RxNorm
Internet RFC 1521 N. Borenstein, N Freed MIME [Multi-
purposeInternet Mail Extensions] Purpose: Mechanisms
3. Terminology
for Specifying and Designating the Format of Internet
Message Bodies Bellcore Innosoft Sept. 1993 3.1 Definitions—Terminology related to general informa-
ANSI/CLSI ASTP2 Point of Care In-vitro Diagnostic Test- tion systems appears inANSI X3.172 andANSI/IEEE 610.12.
ing Terminology relating generally to healthcare information ap-
CLSI AUTO1-A Laboratory Automation: Specimen pears in CEN EN 12264 and CEN EN 12017, Terminology
Container/Specimen Carrier E2457, and Unified Medical Language System (UMLS). The
CLSI AUTO2-A Laboratory Automation: Bar codes for terms used frequently from these sources appear here, in
Specimen Container Identification addition to those terms specific to this practice.
CLSI AUTO3-A Laboratory Automation: Communications
3.2 Definitions of Terms Specific to This Standard:
with Automated Clinical Laboratory Systems, Instru- 3.2.1 health information network, n—set of data domains
ments, Devices and Information Systems
(nodes) and communications pathways (arcs) serving a health-
CLSI AUTO4-A Laboratory Automation: Systems Opera- care constituency with information management services.
tional Requirements, Characteristics and Information El-
3.2.2 identifier, n—symbol used to name, indicate, or lo-
ements cate. ANSI/IEEE 610.12
CLSI AUTO5-A Laboratory Automation: Electromechani-
3.2.2.1 Discussion—Identifiersmaybeassociatedwithsuch
cal Interfaces things as data structures, data items, or program locations.
CLSI LIS-1A Specification for Low Level Protocol to
3.2.3 practitioner, licensed, n—individual at any level of
Transfer Messages between Clinical Laboratory Instru- professional specialization who requires a public license/
ments and Computer Systems certification to practice the delivery of care to patients.
CLSI LIS-2A Specification for Transferring Information E1384
between Clinical Instruments and Computer Systems 3.2.3.1 Discussion—A practitioner may also be a provider.
CLSI LIS-3A Guide for Procurement of a Clinical Labora- 3.2.4 provider, n—business entity that furnishes healthcare
tory Information Management System (CLIMS) to a consumer. E1384
CLSI LIS-5A Specification for Transferring Clinical Obser-
vations between Independent Computer Systems
CLSI LIS-7A Specification for Use of Bar Codes on Speci-
Available from NEMA, Suite 1752, 1300 N. 17th St., Rosslyn, VA 22209.
Available from the Institute of Electrical and Electronics Engineers, Inc., 1828
L St., NW, Suite 1202, Washington, DC 20036-5104.
6 11
Available from the Association for Advancement of Medical Instrumentation, Available from the IUPAC Secretariat, PO Box 13757, Research Triangle
1110 N. Glebe Rd., Suite 220, Arlington, VA 22201-4795. Park, NC 27709-3757.
7 12
Available from the European Committee for Standardization, 36 rue de Available from the National Council for Prescription Drug Programs, 9240 E.
Stassart, B-1050 Brussels, Belgium. Raintree Dr., Scottsdale, AZ 85260-7518.
8 13
AvailablefromtheClinicalandLaboratoryStandardsInstitute,940WestValley Available from Reference and Web Services, National Library of Medicine,
Rd., Suite 1400, Wayne, PA 19087-1898. 8600 Rockville Pike, Bethesda, MD 20894.
E2538 – 06
3.2.4.1 Discussion—This term includes a professionally than a single IDS itself and are buying such services for
licensed practitioner who is authorized to operate a healthcare themselves rather than offering them internally.
delivery facility. 4.3 These organizations will need a frame of reference for
3.3 Acronyms—The following acronyms are used in
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.