openEHR Conformance Certificate
Issuer: openEHR Specification Program | |
---|---|
Release: CNF development |
Status: DEVELOPMENT |
Revision: [latest_issue] |
Date: [latest_issue_date] |
Keywords: conformance, certificate |
© 2021 - 2024 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 |
Creative Commons Attribution-NoDerivs 3.0 Unported. https://creativecommons.org/licenses/by-nd/3.0/ |
Support |
Issues: Problem Reports |
Acknowledgements
This specification was developed and is maintained by the openEHR Specifications Editorial Committee (SEC).
1. Preface
1.1. Purpose
This document defines a template for openEHR Conformance Certificate, a document that is generated as the result of executing a conformance test schedule against a running system or application. This may be a product, or a particular system, e.g. the specific environment of a healthcare provider. The audience of this document includes:
-
Software development organisations developing healthcare information systems;
-
Customer (i.e. procuring) organisations.
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/development/certificate.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
An openEHR Conformance Certificate consists of a rating in the Functional and Content dimensions, and a detailed report. The ratings are as follows:
Characteristics | Levels | Description |
---|---|---|
Functional |
CORE |
Core functionality required for operational deployment. |
STANDARD |
More comprehensive capabilities useful in a 'standard' EHR operational environment. |
|
OPTIONS |
Optional features required in specific circumstances. |
|
Non-functional |
BASIC-SEC |
Basic security features. |
BASIC-PRIV |
Basic privacy features. |
|
External data format |
Canonical XML |
openEHR Canonical XML, defined by published XSDs |
Canonical JSON |
openEHR Canonical XML, defined by published transform of XML |
A generated certificate for a typical system will look as shown in the following section.
Conformance Certificate
System Under Test (SUT)
Solution |
BestEHR release 2.4 |
---|---|
Vendor |
ACME EHR systems LLC, Maxperformancia |
Assessor |
openEHR Foundation |
Infrastructure |
openEHR CNF-test WS 1.5.0 on AWS … |
Date |
12 April 2017 |
Detailed Test Report
SUT Component | openEHR Component | Capability (profile) | Conformance point | Test Case | REST | protobuf |
---|---|---|---|---|---|---|
CDR |
EHR persistence |
EHR Operations |
I_EHR_SERVICE.create_ehr() |
EHR. |
pass |
pass |
Versioning |
I_EHR_COMPOSITION. |
EHR_COMPOSITION. |
pass |
pass |
||
I_EHR_CONTRIBUTION. |
I_EHR_CONTRIBUTION. |
pass |
FAIL |
|||
I_EHR_CONTRIBUTION. |
FAIL |
FAIL |
||||
… |
||||||
etc |
Profile Report
SUT Component |
openEHR Component |
Capability | Required in profile |
Result |
---|---|---|---|---|
K-base |
Definitions |
ADL 1.4 archetype provisioning |
Y |
pass |
ADL 1.4 OPT provisioning |
Y |
pass |
||
Query provisioning |
Y |
pass |
||
CDR |
EHR persistence |
EHR Operations |
Y |
pass |
EHR Status |
Y |
pass |
||
Composition Operations |
Y |
pass |
||
Directory Operations |
Y |
pass |
||
Change Sets |
Y |
pass |
||
Versioning |
Y |
pass |
||
Konsole |
Admin |
Activity Report |
OPT |
FAIL |
Physical Delete |
N |
pass |
||
EHR Archive |
OPT |
pass |
||
… |
||||
etc |