This page provides a list of the FHIR artifacts defined as part of this implementation guide.

Behavior: Capability Statements

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.

Structures: Resource Profiles

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

Example: Example Instances

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