Loading...

XML

Word

Printable

JSON

Details

Type: Change Request
Resolution: Persuasive with Modification
Priority: Medium

Specification:

US Core (FHIR)
Work Group:

US Realm Task Force
Related Page(s):

Profiles and Extensions
Grouping:
Resolution Description:

Hide

Since the time that this comment was created, US Core has added guidance on Basic Provenance and a US Core Provenance profile in version 3.1.1. , in response to USCDI requirements. There is no industry-wide nor regulatory push to expand these requirements to the scope the commenter is proposing.

Show
Since the time that this comment was created, US Core has added guidance on Basic Provenance and a US Core Provenance profile in version 3.1.1. , in response to USCDI requirements. There is no industry-wide nor regulatory push to expand these requirements to the scope the commenter is proposing.
Resolution Vote:
Brett Marquard / John Moehrke: 17-0-1
Change Category:
Enhancement
Change Impact:
Compatible, substantive
Pre Applied:
Yes

Description

1) Require creation/binding of Provenance resource instance at creation, update or deletion event for any other instance(s).

2) Require creation/binding of AuditEvent resource instance at read event for any other instance(s).

Suggest incorporation of, or reference to, Provenance and AuditEvent Profiles as defined for the FHIR EHR System Record Lifecycle Event Implementation Guide (RLE IG).

EHR-S RLE IG: http://hl7.org/fhir/2018Jan/ehrsrle/ehrsrle.html

EHR-S RLE Provenance Profile: http://www.hl7.org/FHIR/2018Jan/ehrsrle/ehrsrle-provenance.html

EHR-S RLE AuditEvent Profile: http://www.hl7.org/FHIR/2018Jan/ehrsrle/ehrsrle-auditevent.html