本文件规定了需要或提供EHR数据的系统和服务之间可互操作通信所需的信息体系结构。本文档不打算指定此类系统的内部架构或数据库设计。要传达的记录或记录摘录的主题是个人，并且传达的范围主要是关于该人的护理。将医疗记录用于其他目的，如行政、管理、研究和流行病学，需要对个人记录进行汇总，这不是本文档的重点，但此类二次使用也可能会发现该文档很有用。本文件定义了一组接口，用于请求和提供:-ISO 13606-1中定义的特定护理对象的EHR_摘录；-ISO 13606-2中定义的一个或多个原型；-ISO 13606-4中定义的特定护理对象的EHR_AUDIT_LOG_摘要。本文档定义了一组交互，用于请求每个人工制品，并向请求方提供数据或拒绝请求。查询一个或多个EHR的接口（例如，用于临床审计或研究）超出了其范围，尽管在请求一个EHR_摘录时规定了某些选择标准，该摘录也可能用于总体查询。本文档定义了每个接口的计算视角，而不指定或限制特定的工程方法来将这些实现为消息或服务接口。本文档有效地定义了要在每个接口上通信的负载。它没有具体说明不同的传输协议将额外需要的特定信息，也没有说明通信各方之间可能商定或不同管辖区要求的安全或认证程序。

This document specifies the information architecture required for interoperable communications between systems and services that need or provide EHR data. This document is not intended to specify the internal architecture or database design of such systems. The subject of the record or record extract to be communicated is an individual person, and the scope of the communication is predominantly with respect to that person's care. Uses of healthcare records for other purposes such as administration, management, research and epidemiology, which require aggregations of individual people's records, are not the focus of this document but such secondary uses could also find the document useful. This document defines a set of interfaces to request and provide: — an EHR_EXTRACT for a given subject of care as defined in ISO 13606-1; — one or more ARCHETYPE(s) as defined in ISO 13606-2; — an EHR_AUDIT_LOG_EXTRACT for a given subject of care as defined in ISO 13606-4. This document defines the set of interactions to request each of these artefacts, and to provide the data to the requesting party or to decline the request. An interface to query an EHR or populations of EHRs, for example for clinical audit or research, are beyond its scope, although provision is made for certain selection criteria to be specified when requesting an EHR_EXTRACT which might also serve for population queries. This document defines the Computational Viewpoint for each interface, without specifying or restricting particular engineering approaches to implementing these as messages or as service interfaces. This document effectively defines the payload to be communicated at each interface. It does not specify the particular information that different transport protocols will additionally require, nor the security or authentication procedures that might be agreed between the communicating parties or required by different jurisdictions.