openEHR logo

openEHR Platform Profiles

Issuer: openEHR Specification Program

Release: CNF latest

Status: DEVELOPMENT

Revision: [latest_issue]

Date: [latest_issue_date]

Keywords: conformance, profile, product

openEHR components
© 2022 - 2022 The openEHR Foundation

The openEHR Foundation is an independent, non-profit foundation, facilitating the sharing of health records by consumers and clinicians via open specifications, clinical models and open platform implementations.

Licence

image Creative Commons Attribution-NoDerivs 3.0 Unported. https://creativecommons.org/licenses/by-nd/3.0/

Support

Issues: Problem Reports
Web: specifications.openEHR.org

Amendment Record

Issue Details Raiser Completed

CNF Release 1.0.?

0.5.0

SPECCNF-1: Initial Writing; extracted from Platform Test Schedule.

T Beale

07 Jan 2022

Acknowledgements

This specification was developed and is maintained by the openEHR Specifications Editorial Committee (SEC).

Principal Authors

Trademarks

  • 'openEHR' is a trademark of the openEHR Foundation

1. Preface

1.1. Purpose

This document specifies the openEHR Platform profiles, which may be used to scope conformance testing of openEHR platform products. The audience of this document includes:

  • Software development organisations developing healthcare information systems;

  • Customer (i.e. procuring) organisations.

Useful references for reading this document include:

1.3. Status

This specification is in the DEVELOPMENT state. The development version of this document can be found at https://specifications.openehr.org/releases/CNF/latest/profiles.html.

Known omissions or questions are indicated in the text with a 'to be determined' paragraph, as follows:

TBD: (example To Be Determined paragraph)

1.4. Feedback

Feedback may be provided on the openEHR Conformance forum.

Issues may be raised on the specifications Problem Report tracker.

To see changes made due to previously reported issues, see the CNF component Change Request tracker.

2. Overview

The Platform X Conformance Test Schedule describes capabilities of openEHR platform products that can be tested against the published specifiations. These capabilities are grouped into profiles to provide a guide to what constitutes the required functionality for particular category of solution.

A profile may be defined logically as a particular list of platform components and capabilities that may be combined to specify a particular kind of solution. For example, an openEHR Demographics product would treat most or all of the Demographic capabilities as mandatory, along with support for definitions, logging etc.

This specification defines a set of default profiles intended as a guide for determining the minimum capabilities to specify in order to obtain certain basic levels of functionality.

Producers of tender specifications and procuring organsations should create the Profile(s) they require. This should be done by adopting either the CORE or STANDARD base profiles and then adding in the set of options required.

3. Default Profiles

The default product profiles defined are as follows:

  • CORE: a minimal functional openEHR platform implementation that enables the storage and retrieval of openEHR EHR data;

  • STANDARD: a 'standard' configuration of capabilities that adds AQL querying and logging to the CORE;

  • OPTIONS: components that are considered optional for non-specialised solutions.

In order to obtain CORE or STANDARD conformance, all mentioned capabilities must be met in testing. The OPTIONS profile is a catch-all pseudo-profile that covers all testable capabilities not included in CORE or STANDARD; OPTIONS is obtained if any optional capability is passed in testing.

3.1. Functional

Product Component Capability CORE STANDARD OPTIONS

Definitions

ADL 1.4 Archetype
provisioning

ADL 1.4 OPT
provisioning

ADL 2 Archetype
provisioning

ADL 2 OPT
provisioning

Query
provisioning

EHR
Persistence

EHR Operations

EHR Status

Composition
Operations

Directory
Operations

Change sets

Versioning

Archetype
Validation

Demographic
Persistence

Party Operations

Party
Relationship
Operations

Archetype
validation

Querying

AQL basic

AQL advanced

AQL & terminology

Admin

Activity Report

Physical Deletion

EHR Dump/Load

Bulk EHR load

EHR Archive

Demographic Archive

Messaging

EHR Extract

TDS

REST APIs

DEFINITION API

EHR API

DEMOGRAPHIC API

QUERY API

ADMIN API

MESSAGE API

3.2. Non-Functional

Product Attribute Capability CORE STANDARD OPTIONS

Security &
Privacy

Signing

Anonymous EHRs

3.3. Other Non-Functional

Product Attribute Values

External Data Format

XML, JSON