EHR and PHR System Functional Models - Record Lifecycle Events Implementation Guide, published by HL7 International / Electronic Health Records. This guide is not an authorized publication; it is the continuous build for version 1.2.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/ehrs-rle-ig/ and changes regularly. See the Directory of published versions
Contents:
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
The following artifacts define the specific capabilities that different types of systems are expected to have in order to comply with this implementation guide. Systems conforming to this implementation guide are expected to declare conformance to one or more of the following capability statements.
EHRS Functional Model - Record Lifecycle Events - Capability Statement |
This profile defines the expected capabilities of an ''Electronic Health Record System'' when conforming to the EHRS functional model's Record Lifecycle specification. |
These define constraints on FHIR resources for systems conforming to this implementation guide.
EHRS Functional Model - Record Lifecycle Events - AuditEvent |
Defines the elements to be supported within the AuditEvent resource in order to conform with the Electronic Health Record System Functional Model Record Lifecycle Event standard |
EHRS Functional Model - Record Lifecycle Events - Provenance |
Defines the elements to be supported within the Provenance resource in order to conform with the Electronic Health Record System Functional Model Record Lifecycle Event standard |
These define sets of codes used by systems conforming to this implementation guide.
ValueSet record-lifecycle-events |
Record Lifecycle Events ValueSet |
These define new code systems used by systems conforming to this implementation guide.
CodeSystem record-lifecycle-events |
Record Lifecycle Events CodeSystem - new events |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.
Originate/Retain Order - AuditEvent |
Example for EHR-S FM R2.1 RI.1.1.1 |
Originate/Retain Order - Provenance |
Example for EHR-S FM R2.1 RI.1.1.1 |