ANSI ASTM E2553-2007 Standard Guide for Implementation of a Voluntary Universal Healthcare Identification System《自动通用卫生保健识别系统实施用指南》.pdf
《ANSI ASTM E2553-2007 Standard Guide for Implementation of a Voluntary Universal Healthcare Identification System《自动通用卫生保健识别系统实施用指南》.pdf》由会员分享,可在线阅读,更多相关《ANSI ASTM E2553-2007 Standard Guide for Implementation of a Voluntary Universal Healthcare Identification System《自动通用卫生保健识别系统实施用指南》.pdf(14页珍藏版)》请在麦多课文档分享上搜索。
1、Designation: E2553 07 (Reapproved 2013)Standard Guide forImplementation of a Voluntary Universal HealthcareIdentification System1This standard is issued under the fixed designation E2553; the number immediately following the designation indicates the year oforiginal adoption or, in the case of revis
2、ion, 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 document describes the implementation principlesneeded to create a Voluntary Universal Healthcar
3、e Identifica-tion (VUHID) system. The purpose of this system is to enableunambiguous identification of individuals in order to facilitatethe delivery of healthcare.1.2 The VUHID system should be dedicated exclusively tothe needs and functions of healthcare.1.3 The VUHID system is designed to represe
4、nt no, or atleast minimal, increased risk to healthcare privacy and security.1.4 The system should be as cost-effective as possible.1.5 The system must be created and maintained in a way toprovide sustained benefit to healthcare.1.6 The system should be designed and implemented in amanner that ensur
5、es that it can operate indefinitely.1.7 This standard does not purport to address all of thesafety concerns, if any, associated with its use. It is theresponsibility of the user of this standard to establish appro-priate safety and health practices and determine the applica-bility of regulatory limi
6、tations prior to use.1.8 This international standard was developed in accor-dance with internationally recognized principles on standard-ization established in the Decision on Principles for theDevelopment of International Standards, Guides and Recom-mendations issued by the World Trade Organization
7、 TechnicalBarriers to Trade (TBT) Committee.2. Referenced Documents2.1 ASTM Standards:2E1714 Guide for Properties of a Universal Healthcare Iden-tifier (UHID)2.2 Other Standard:AIIM Standard PDF417 Bar-coding3. Terminology3.1 Acronyms:3.1.1 2Dtwo dimensional3.1.2 CDOcare delivery organization3.1.3 E
8、MPIenterprise master patient index3.1.4 MOmanaging organization3.1.5 OVIDopen voluntary healthcare identifier3.1.6 PVIDprivate voluntary healthcare identifier3.1.7 VUHIDvoluntary universal healthcare identification4. Summary of Guide4.1 The VUHID facility described in this guide is respon-sible for
9、issuing unique personal healthcare identifiers to anycooperating EMPI facility (defined below) upon receipt of anauthenticated request. The issued identifiers must be consistentwith Guide E1714 and, as appropriate, would consist of bothopen OVIDs (Open Voluntary Healthcare Identifiers) as wellas PVI
10、Ds (Private Voluntary Healthcare Identifiers). Thisdocument will refer to any identifier issued by the VUHID,whether OVID or PVID, as a VUHID identifier. OVIDs areused to provide linkage of healthcare information for circum-stances where the identity of the associated person is meant tobe freely acc
11、essible. PVIDs (which exist in various privacyclasses) permit linkage of various healthcare data items wherethe identity of the associated individual is not meant to bepublicly available.4.2 The VUHID system should be created as a securehigh-availability server on the Internet which communicatesexcl
12、usively with cooperating EMPI facilities using securecommunication techniques. The VUHID facility issues identi-fiers and is responsible for maintaining policies and proceduresrelating to various classes of PVIDs. It does not store patientidentification, demographic information, or clinical informa-
13、tion and for this reason does not represent a security or privacyvulnerability. (See Section 12 for a description of how thisapproach is implemented when issuing a new identifier.) TheVUHID facility should receive requests for information relat-ing to a given identifier and distribute those requests
14、 to all1This guide is under the jurisdiction of ASTM Committee E31 on HealthcareInformatics and is the direct responsibility of Subcommittee E31.35 on HealthcareData Analysis.Current edition approved March 1, 2013. Published March 2013. Originallyapproved in 2007. Last previous edition approved in 2
15、007 as E255307. DOI:10.1520/E2553-07R13.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.Copyright ASTM Intern
16、ational, 100 Barr Harbor Drive, PO Box C700, West Conshohocken, PA 19428-2959. United StatesThis international standard was developed in accordance with internationally recognized principles on standardization established in the Decision on Principles for theDevelopment of International Standards, G
17、uides and Recommendations issued by the World Trade Organization Technical Barriers to Trade (TBT) Committee.1cooperating EMPI facilities in order to fulfill the informationsharing goals associated with unambiguous patient identifica-tion.4.3 The identifiers issued by the VUHID facility can beused,
18、consistent with the policy established for each identifierclass, by all of the participating healthcare facilities interactingwith a cooperating EMPI to facilitate storage, linkage, andexchange within that system.4.4 The VUHID facility should be controlled by a managingorganization that is dedicated
19、 exclusively to the benefit of thehealthcare industry.5. Significance and Use5.1 This standard describes a proposal to provide unambigu-ous personal identification for any patient who requests it. Intodays world of specialized healthcare and mobile patients it istypical for clinical information on a
20、 single patient to reside ina variety of locations, some using manual data storagetechniques, but an increasing number using electronic means.In order for a clinician to provide safe and appropriate clinicalcare in this environment it is necessary to be able to aggregateappropriate clinical informat
21、ion on a specific patient in order togain an accurate and comprehensive picture of that patientsclinical situation. This implies that all information relating toeach patient should be identified in a unique manner tofacilitate the process of accurately aggregating appropriateinformation.5.2 The conv
22、erse of the need for data aggregation is thepatients need to protect the privacy of their information.Unless patients are confident that they can avoid inappropriatesharing of clinical information they will not readily share thatinformation with caregivers. Thus, the same system thatsupports unambig
23、uous linkage of all information concerning apatient must also play a role in protecting the privacy of thatinformation.5.3 The proposed patient identification system must be ableto avoid or overcome the numerous objections that haveprevented implementation of a universal patient identificationsystem
24、 in the past including issues related to:5.3.1 TechnologyThe proposed system must be techni-cally feasible in a manner that promotes scalability,availability, and ease of implementation.5.3.2 Integration with Existing SystemsTo the maximumextent possible the proposed identification system should wor
- 1.请仔细阅读文档,确保文档完整性,对于不预览、不比对内容而直接下载带来的问题本站不予受理。
- 2.下载的文档,不会出现我们的网址水印。
- 3、该文档所得收入(下载+内容+预览)归上传者、原创作者;如果您是本文档原作者,请点此认领!既往收益都归您。
下载文档到电脑,查找使用更方便
5000 积分 0人已下载
下载 | 加入VIP,交流精品资源 |
- 配套讲稿:
如PPT文件的首页显示word图标,表示该PPT已包含配套word讲稿。双击word图标可打开word文档。
- 特殊限制:
部分文档作品中含有的国旗、国徽等图片,仅作为作品整体效果示例展示,禁止商用。设计者仅对作品中独创性部分享有著作权。
- 关 键 词:
- ANSIASTME25532007STANDARDGUIDEFORIMPLEMENTATIONOFAVOLUNTARYUNIVERSALHEALTHCAREIDENTIFICATIONSYSTEM 自动

链接地址:http://www.mydoc123.com/p-432633.html