GAO Ballot Package

This page is part of the FHIR Specification (v1.1.0: STU 3 Ballot 1). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R4 R3 R2

This is a frozen snapshot of the FHIR specification created for the purpose of balloting the GAO implementation Guide. It includes draft changes that may be part of the future DSTU 2.1 release but further change is expected. Readers should focus solely on the GAO implementation content, and FHIR DSTU 2 for other purposes.

Conformance-ehrs-rle

This is the narrative for the resource. See also the XML or JSON format.

Record Lifecycle-conformant Electronic Health Record System

(Requirements Definition)

Published: 2014-12-06 (draft)

Published by: Health Level Seven, Int'l - Electronic Health Record work group

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

General

FHIR Version:	0.2
Supported formats:	xml, json

REST behavior

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

Resource

Search

Read

Read Version

Instance History

Resource History

Validate

Create

Update

Delete

Provenance

Yes

AuditEvent

Yes

Provenance

Interactions

Name	Description
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'.

AuditEvent

Interactions

Name	Description
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'.

Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.