EHR and PHR System Functional Models - Record Lifecycle Events Implementation Guide
1.2.0 - Informative Release 2 International flag

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

CapabilityStatement: EHRS Functional Model - Record Lifecycle Events - Capability Statement

Official URL: http://hl7.org/fhir/uv/ehrs-rle/CapabilityStatement/conformance-ehrs-rle Version: 1.2.0
Standards status: Informative Maturity Level: 1 Computable Name: EHRSFunctionalModelRecordLifecycleEventsCapabilityStatement

This profile defines the expected capabilities of an ''Electronic Health Record System'' when conforming to the EHRS functional model's Record Lifecycle specification.

Raw OpenAPI-Swagger Definition file | Download

Generated Narrative: CapabilityStatement conformance-ehrs-rle

EHRS Functional Model - Record Lifecycle Events - Capability Statement

  • Implementation Guide Version: 1.2.0
  • FHIR Version: 6.0.0-ballot2
  • Supported Formats: xml, json
  • Supported Patch Formats:
  • Published on: 2024-12-11 17:05:48+0000
  • Published by: HL7 International / Electronic Health Records

Note to Implementers: FHIR Capabilities

Any FHIR capability may be 'allowed' by the system unless explicitly marked as 'SHALL NOT'. A few items are marked as MAY in the Implementation Guide to highlight their potential relevance to the use case.

FHIR RESTful Capabilities

Mode: client

Conformant systems must record [[Provenance]] records on all Create, Update and Delete actions on any resource other than Provenance or AuditEvent. Conformant systems must record [[AuditEvent]] records on all Create, Update and Delete actions as well as all GET operations (read, search, etc.)

Security

Any security rules??

Summary of System-wide Interactions

Capabilities by Resource/Profile

Summary

The summary table lists the resources that are part of this configuration, and for each resource it lists:

  • The relevant profiles (if any)
  • The interactions supported by each resource (Read, Search, Update, and Create, are always shown, while VRead, Patch, Delete, History on Instance, or History on Type are only present if at least one of the resources has support for them.
  • The required, recommended, and some optional search parameters (if any).
  • The linked resources enabled for _include
  • The other resources enabled for _revinclude
  • The operations on the resource (if any)
Resource TypeProfileRSUCSearches_include_revincludeOperations
Provenancehttp://hl7.org/fhir/uv/ehrs-rle/StructureDefinition/ehrsrle-provenancey
AuditEventhttp://hl7.org/fhir/uv/ehrs-rle/StructureDefinition/ehrsrle-auditeventy

Resource Conformance: SHALL Provenance

Base System Profile
EHRS Functional Model - Record Lifecycle Events - Provenance
Profile Conformance
SHALL
Reference Policy

Interaction summary
  • SHALL support
    create

    Allows defining a new data element. Repositories requiring curation of submitted data elements may require all new data elements to have a status of 'draft'.

Resource Conformance: SHALL AuditEvent

Base System Profile
EHRS Functional Model - Record Lifecycle Events - AuditEvent
Profile Conformance
SHALL
Reference Policy

Interaction summary
  • SHALL support
    create

    Allows defining a new data element. Repositories requiring curation of submitted data elements may require all new data elements to have a status of 'draft'.