TM_E_1715_
_01_2013
Designation:E171501(Reapproved 2013)An American National StandardStandard Practice forAn Object-Oriented Model for Registration,Admitting,Discharge,and Transfer(RADT)Functions in Computer-Based Patient Record Systems1This standard is issued under the fixed designation E1715;the number immediately following the designation indicates the year oforiginal adoption or,in the case of revision,the year of last revision.A number in parentheses indicates the year of last reapproval.Asuperscript epsilon()indicates an editorial change since the last revision or reapproval.1.Scope1.1 This practice is intended to amplify Practice E1239 andto complement Practice E1384 by detailing the objects thatmake up the reservation,registration,admitting,discharge,andtransfer(RADT)functional domain of the computer-basedrecord of care(CPR).As identified in Practice E1239,thisdomain is seminal to all patient record and ancillary systemfunctions,including messaging functions used in telecommu-nications.For example,it is applicable to clinical laboratoryinformation management systems,pharmacy information man-agement systems,and radiology,or other image management,information management systems.The object model terminol-ogy is used to be compatible with other national and interna-tional standards for healthcare data and information systemsengineering or telecommunications standards applied to health-care data or systems.This practice is intended for thosefamiliar with modeling concepts,system design,and imple-mentation.It is not intended for the general computer user or asan initial introduction to the concepts.2.Referenced Documents2.1 ASTM Standards:2E1238 Specification for Transferring Clinical ObservationsBetween Independent Computer Systems(Withdrawn2002)3E1239 Practice for Description of Reservation/Registration-Admission,Discharge,Transfer(R-ADT)Systems forElectronic Health Record(EHR)SystemsE1384 Practice for Content and Structure of the ElectronicHealth Record(EHR)E1633 Specification for Coded Values Used in the ElectronicHealth RecordE1639 Guide for Functional Requirements of Clinical Labo-ratory Information Management Systems(Withdrawn2002)3E1744 Practice for View of Emergency Medical Care in theElectronic Health RecordF1629 Guide for Establishing Operating Emergency Medi-cal Services and Management Information Systems,orBoth2.2 ANSI Standard:ANSI X3.172 Dictionary of Information Systems42.3 IEEE Standard:IEEE 1157.1 Trial Use Standard for Healthcare InformationInterchangeInformation Modelling(6 June 1994)52.4 Other Document:HL-7 v2.4 Data Communication Standard63.Terminology3.1 DefinitionsGeneral terms are defined in accordancewith ANSI X3.172.3.2 Definitions of Terms Specific to This Standard:3.2.1 functional domain,nthat area of activity that encom-passes a given function.(HL-7,v2.4)3.2.2 healthcare domain,nthat functional domain encom-passing all aspects of the delivery of health care,both preven-tive and corrective,to patients,and the management ofresources enabling that care to be delivered.(HL-7,v2.4)4.Background4.1 Object Representation of RADT ProcessesPracticeE1239 provides the experiential background of the functions inRADT.These functions are common to all systems that dealwith patient data.The minimal essential data elements for1This practice is under the jurisdiction of ASTM Committee E31 on HealthcareInformatics and is the direct responsibility of Subcommittee E31.25 on HealthcareData Management,Security,Confidentiality,and Privacy.Current edition approved March 01,2013.Published March 2013.Originallyapproved in 1995.Last previous edition approved in 2008 as E1715 01(2008).DOI:10.1520/E1715-01R13.2For referenced ASTM standards,visit the ASTM website,www.astm.org,orcontact ASTM Customer Service at serviceastm.org.For Annual Book of ASTMStandards volume information,refer to the standards Document Summary page onthe ASTM website.3The last approved version of this historical standard is referenced onwww.astm.org.4Available from American National Standards Institute(ANSI),25 W.43rd St.,4th Floor,New York,NY 10036,http:/www.ansi.org.5Available from Institute of Electrical and Electronics Engineers,Inc.(IEEE),445 Hoes Ln.,P.O.Box 1331,Piscataway,NJ 08854-1331,http:/www.ieee.org.6Available from Health Level Seven,900 Victors Way,Suite 122,AnnArbor,MI48108.Copyright ASTM International,100 Barr Harbor Drive,PO Box C700,West Conshohocken,PA 19428-2959.United States1 RADT were identified and characterized partly in PracticeE1239.Table 1 of that guide identifies a logical data structurefor the data elements,but it does not relate these elements toconstituent“entities”or“objects”in the sense that they arenow used in analysis.Entity-relationship modeling is onemajor technique used(1)7to establish the conceptual“things”and their relationships involved in this overall functionaldomain.“Objects”(2,3)is another term for these things,andthe object concept involves very specific characteristics asso-ciated with a defined object such