DSTU2 STU 3 Ballot
This page is part of the FHIR Specification (v1.0.2: DSTU 2). The current version which supercedes this version is

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

1.6 2.12 Outstanding Issues Outstanding Issues This specification is currently in its second round of trial use. Much work remains to be done. Specifically, there are still many outstanding questions about the Request/Fulfillment cycle ( Order / OrderResponse and how various statuses and workflows associated with requests, as well as how proposals cascade to plans to orders to downstream/encoded orders, etc. This is a matter of ongoing investigation. In addition, the following general areas of functionality have been deferred to a future version: Adverse Event Reporting An alarm resource to represent current issues with the patient (e.g. device created) Concern Tracking Clinical Studies and Protocols Aggregated Data Reporting including Public Health Reporting Payment related resources, and specifically, an Account resource for payment tracking One or more resources for Advance Care Directive / Power of Attorney Use of RDF A full server side query framework For some of these, some draft content is included in the specification for implementer consideration. In addition, there are a number of specific notes in the specification requesting feedback from implementers:

This specification is currently approaching its third round of trial use. While some parts of the specification are mature and stable, much work remains to be done. The following general areas of functionality have been deferred to a future version:

  • Adverse Event Reporting
  • An alarm resource to represent current issues with the patient (e.g. device created)
  • Concern Tracking
  • Clinical Studies and Protocols
  • Aggregated Data Reporting including Public Health Reporting
  • Payment related resources, and specifically, an Account resource for payment tracking
  • One or more resources for Advance Care Directive / Power of Attorney
  • A full server side query framework

For some of these, some draft content is included in the specification for implementer consideration.

In addition, there are a number of specific notes in the specification requesting feedback from implementers: