scope:

This standard specifies the information architecture required for interoperable communications between systems and services that need or provide EHR data. This standard 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 standard but such secondary uses could also find the standard useful. Part 5 of this standard defines a set of interfaces to request and provide:- an EHR_EXTRACT for a given subject of care as defined in Part 1 of this standard;- one or more ARCHETYPE(s) as defined in Part 2 of this standard;- an EHR_AUDIT_LOG_EXTRACT for a given subject of care as defined in Part 4 of this standard.Part 5 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 also 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.Part 5 defines the Computational Viewpoint for each interface, without specifying or restricting particular engineering approaches to implementing these as messages or as service interfaces.Part 5 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 that might be agreed between the communicating parties or required by different jurisdictions.