HOME   Cart(0)   Quotation   About-Us Policy PDFs Standard-List
www.ChineseStandard.net Database: 189759 (19 Oct 2025)

GB/T 24466-2009 English PDF

US$534.00 · In stock
Delivery: <= 4 days. True-PDF full-copy in English will be manually translated and delivered via email.
GB/T 24466-2009: Health informatics -- Requirements for an electronic health record architecture
Status: Valid
Standard IDContents [version]USDSTEP2[PDF] delivered inStandard Title (Description)StatusPDF
GB/T 24466-2009English534 Add to Cart 4 days [Need to translate] Health informatics -- Requirements for an electronic health record architecture Valid GB/T 24466-2009

PDF similar to GB/T 24466-2009


Standard similar to GB/T 24466-2009

GB/T 36388   YBB 00022003   YBB 00032003   GB/T 45938   GB/Z 24464   GB/T 24465   

Basic data

Standard ID GB/T 24466-2009 (GB/T24466-2009)
Description (Translated English) Health informatics -- Requirements for an electronic health record architecture
Sector / Industry National Standard (Recommended)
Classification of Chinese Standard C07
Classification of International Standard 35.240.80
Word Count Estimation 27,249
Date of Issue 2009-10-15
Date of Implementation 2009-12-01
Quoted Standard GB/T 5271.8-2001; ISO/TS 17090-1-2002; ASTME 1769-1995; ENV 13606-1-2000; CPRI-1995; EU-CEN-1997; FEAF-2001; OHIH-2001; ZACHMAN-1996
Adopted Standard ISO/TS 18308-2004, IDT
Regulation (derived from) National Standard Approval Announcement 2009 No.11 (Total No.151)
Issuing agency(ies) General Administration of Quality Supervision, Inspection and Quarantine of the People's Republic of China, Standardization Administration of the People's Republic of China
Summary This standard specifies the electronic health record architecture (EHRA) is a collection of clinical and technical requirements to support cross-sectoral, cross-country and cross- service model of health care use, sharing and exchange of electronic health records. This standard gives the architecture of demand rather than architecture itself.

GB/T 24466-2009: Health informatics -- Requirements for an electronic health record architecture

---This is a DRAFT version for illustration, not a final translation. Full copy of true-PDF in English version (including equations, symbols, images, flow-chart, tables, and figures etc.) will be manually/carefully translated upon your order.
Health informatics. Requirements for an electronic health record architecture ICS 35.240.80 C07 National Standards of People's Republic of China GB/T 24466-2009/ISO /TS18308.2004 Health Informatics Electronic health record architecture needs (ISO /T S18308.2004, IDT) Posted 2009-10-15 2009-12-01 implementation Administration of Quality Supervision, Inspection and Quarantine of People's Republic of China Standardization Administration of China released

Table of Contents

Preface Ⅰ Introduction Ⅱ 1 Scope 1 2 Normative references 1 3 Terms and definitions 4 EHR architecture framework needs 6 5 EHR system architecture requirements 8 5.1 STR1 --- Structure 8 5.2 PRO2 --- Procedure 11 Communication 12 5.3 COM3 --- 5.4 PRS4 --- Privacy and Security 13 5.5 MEL5 --- Law 14 5.6 ETH6 --- Ethics 15 5.7 COC7 --- Consumer/Culture 15 5.8 EVO8 --- Evolution 16 Appendix A (informative) This standard approach 17 References 19 GB/T 24466-2009/ISO /TS18308.2004

Foreword

This standard is identical with ISO /T S18308.2004 "Health informatics - Electronic health record architecture needs." Appendix A of this standard is an informative annex. The standard proposed by China National Institute of Standardization. The standard by the China National Institute of Standardization. This standard drafting units. China National Institute of Standardization, Chengdu Institute of Standardization, China Armed Police Force Command College, China Population and Development Development Research Center, Chinese PLA General Hospital. The main drafters of this standard. Ren Guanhua, continuous Dong, Chen Huang, Shi Lijuan, book Yin Rui, Zhang Rui, Hu Changchuan, Yun Li Yu, Yu Hua, Liu Shengnan. GB/T 24466-2009/ISO /TS18308.2004

Introduction

0.1 Summary For EHR (electronic health record) system (or any other application) prior to the preparation of a computer program, you must have a clear and detailed Collection of user requirements and technical requirements. In other words, you must use, share and exchange electronic health records to develop a clear and detailed A collection of user and technical requirements EHR architecture. EHR architecture developed EHR systems should be independent of the technology used, but also It should be independent of the current organizational structure. Many health information specialists and health care professionals believe that the world can develop a widely The EHR architecture with international standards. However, this is only the first requirement of this standard is described in detail and agreed love Can be achieved under the conditions. This is the main purpose of the development of this standard. In the past decade, the international community has EHR system architecture requirements for the public sector to carry out a lot of work. Broadly speaking, true Being able to EHR worldwide demand applications should make sure it among the clinical staff in all disciplines, across the health sector, transnational Home health care services across the model used, shared and exchanged. It also supports such research, epidemiology, population health, health management, finance and Health Programme and other second-tier application. Finally, it should be easy to retrofit existing systems and new systems development. 0.2 EHR definition of interpretation Before defining EHR architecture, it is first necessary to reach a consensus on the definition and scope of the EHR. But so far not tangible Into a unified EHR definition. Chapter 3 lists the EHR definitions given in multiple organizations. These definitions are some very simple, some very Long, and contain the scope is not the same. These definitions are more or less because the initial reference EHR different names, including EHCR (E- lectronicHealthCareRecord, electronic health records), EPR (ElectronicPatientRecord, electronic patient records), CPR (ComputerizedPatientRecord computerized patient record) and EMR (ElectronicMedicalRecord, electronic disease calendar). As we all know, these terms have different meanings in different countries and health sectors (for example, that the NHS in England There are obvious differences between EHR and EPR), so this standard requirements are usually covers all the difference. 0.3 EHR architecture description In this standard, electronic health record architecture (EHRA) substantially defined as follows. "Establishment of the information model, which defines the general structure of all EHR member." More detailed explanatory defined as follows. General characteristics of the model of electronic health records are required. The record is transmitted, complete and available and have the force of law Nursing records, and can be cross-system, cross-country and over time to maintain its integrity. EHRA does not require or specify the health care records Content should be stored, there is no provision or specific electronic health record systems operate. [It] records (including those without a copy Paper records) data types without any restrictions. Details "field length" and the like, such as a physical database-wide, and electronic Healthcare Record architecture-independent. [EU-CEN.1997] It should be noted that the definition of the exclusions and more able to explain the EHR architecture (including adapted to different purposes for different EHR) role. For example, the above definition of EHR architecture is not against any country or regional health care system, but also The record does not provide information on particle size (or range) or a temporary property records. Record hospital intensive care ward was a record, And it may be more trivial than the longitudinal primary care records, but are in line with this standard EHR architecture built. EHR architecture should apply to all healthcare sectors, professional health care disciplines and health care service delivery. "Consumer" or "individual" should be consistent with the traditional EHR EHR same EHR architecture, the architecture by the medical specialists, nurses, GB/T 24466-2009/ISO /TS18308.2004 Doctors and health care providers to use. The same EHR architecture should apply to all of the EHR, whether they are called EMR, EHCR, EPR, CPR, PHR or other name. Open standardized EHR architecture is the key to interoperate on the information level. Standardized EHR architecture enables the entire Or part of the EHR between authorized members of multidisciplinary care teams to share and exchange, independent of EHR systems including patient/consumer By. EHR information in line with a standardized EHR architecture EHR systems should be receiving, processing and submission. The EHR system uses The EHR architecture and EHR systems rely source applications or operating systems, databases and hardware. 0.4 This standard methodology The standard EHR needs is summarized in a number of thirty basic source derived, these sources is through extensive literature search and members States to provide material built up. The initial collection of more than seven hundred source requirements by eliminating duplicate requirements specification and obviously with EHR EHR systems rather than related needs, and finally reduced to about six hundred source of demand. Demand for different types of title hierarchy framework is in Develop and refine the project out. The last phase of the project is to develop a small collection of 123 fixed demand component, the collection package Contained in a large source set of requirements, and use a uniform presentation format. On methodological background in Appendix A. "EHR purpose" and "support EHR principle" The following two sections from the source material EHR requirements. "EHR purpose" Mainly due GEHR-08-1994, and made some modifications. "EHR supports the principle of" a combination of a number of source materials meet the initial requirements material. Here also we are given from the EHR design principles (openEHR, 2002) list of EHR features. These three parts according to the EHR system System features and functions of this standard provides a more detailed context, which defines the EHRA must support EHR systems. 0.5 EHR purpose The main purpose is to give a nursing EHR documents record that the present and the future can be the same or different physician care to mention For support. This document is a clinical medical patient care provides a means of communication. The first layer is the beneficiary of EHR patient / Consumer and clinical staff. Like with other beneficiaries, the use of medical records for other purposes is the purpose of the second layer. Many are based on the content of EHR The second layer defining purpose, because the purpose of the information collected in accordance with a first layer of the second layer for many purposes (such as payment, policies and plans, EC Analysis meter, license, etc.) is not sufficient. EHR second layer applications include. --- Application of the law. the evidence provided care to comply with legal proof, reflecting clinical staff qualifications; --- Quality management. continuous quality improvement studies, review of performance monitoring (peer review, clinical audit, the results of the analysis), benchmarking Test, qualification; --- Education. Student training for health professionals, patients/consumers and clinical medical staff; --- Study. New diagnostic modality, disease prevention and treatment, epidemiological research, population health research and assessment analyzes; --- Public health and population health; --- Policy Development. Health statistical analysis, trend analysis, case classification analysis; --- Health Services Administration. resource allocation and management, cost management, reports and publications, marketing strategies, enterprise risk management; --- Bills/finance/compensation. the insurance industry, government agencies, funding agencies. Note. Many applications require a second layer to increase EHR EHR data not contained. 0.6 supports the principle of EHR Regardless of the health care model, EHR should be timely, reliable, complete, accurate, secure and accessible, and can be used to support Health care. EHR should respecting local customs, language and cultural situation truly global interoperability. EHR should not be considered only for patients (ie people with some pathology). More accurate view is that, EHR is the individual concerned Health, including normal and diseased conditions. GB/T 24466-2009/ISO /TS18308.2004 EHR recognized individual health data may be scattered in different systems as well as around the world. In order to achieve data integration, EHR requirements The corresponding system using a common information model, and maximize the use of relevant international standards. In order to develop an effective EHR standards should be clearly defined and non-EHR part part in the standardization work. 0.7 EHR features --- EHR patient/consumer-centric, should ideally include all types of health service personnel (including health professionals Member), and the patient's own emergency services and other related information. This service provider-centric or just mere fragment record in contrast; --- EHR involves observing (has happened), viewpoint (decision on what will happen) and care plan (about what will happen Plans); --- Information EHR extract layer is general information, that is, such as images, professional guide or decision support algorithms such information is not It is a typical part of the EHR, but the interface with other professional systems Standard should exist. --- EHR contains diagnostic tests and other data; --- EHR for personal care, decision support, research purposes, government departments, agencies and other entities to provide statistical information on the clinical source; --- EHR is a patient-related, long-term accumulation of information. GB/T 24466-2009/ISO /TS18308.2004 Health Informatics Electronic health record architecture needs

1 Scope

This standard gives the electronic health record architecture (EHRA) clinical and technical requirements set to support cross-sectoral and cross-border And home health care services across the model to use, share and exchange electronic health records. This standard gives the architecture of demand rather than the architecture itself.

2 Normative references

The following terms and definitions apply to this standard. 3.1 It means a guarantee of that resource data processing system only by authorized entity authorized by way of access. [GB/T 5271.8-2001] 3.2 A characteristic that can ensure an entity's operations can be uniquely traced back to the entity. [GB/T 5271.8-2001] GB/T 24466-2009/ISO /TS18308.2004

Tips & Frequently Asked Questions:

Question 1: How long will the true-PDF of GB/T 24466-2009_English be delivered?

Answer: Upon your order, we will start to translate GB/T 24466-2009_English as soon as possible, and keep you informed of the progress. The lead time is typically 2 ~ 4 working days. The lengthier the document the longer the lead time.

Question 2: Can I share the purchased PDF of GB/T 24466-2009_English with my colleagues?

Answer: Yes. The purchased PDF of GB/T 24466-2009_English will be deemed to be sold to your employer/organization who actually pays for it, including your colleagues and your employer's intranet.

Question 3: Does the price include tax/VAT?

Answer: Yes. Our tax invoice, downloaded/delivered in 9 seconds, includes all tax/VAT and complies with 100+ countries' tax regulations (tax exempted in 100+ countries) -- See Avoidance of Double Taxation Agreements (DTAs): List of DTAs signed between Singapore and 100+ countries

Question 4: Do you accept my currency other than USD?

Answer: Yes. If you need your currency to be printed on the invoice, please write an email to [email protected]. In 2 working-hours, we will create a special link for you to pay in any currencies. Otherwise, follow the normal steps: Add to Cart -- Checkout -- Select your currency to pay.