This page is part of the FHIR Specification (v1.0.2: DSTU (v3.0.2: STU 2). 3). 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: R5 R4B R4 R3 R2 R3 R2

1.6 2.19 Outstanding Issues

This specification is currently in its second third round of trial use. Much work remains to be done. Specifically, there are still many outstanding questions about While some parts of the Request/Fulfillment cycle ( Order / OrderResponse specification are mature and how various statuses stable, and workflows associated with requests, as well as how proposals cascade to plans to orders to downstream/encoded orders, etc. This HL7 is focusing on moving these to a matter of ongoing investigation. In addition, the formal standard, much work remains to be done in other areas. The following general areas of functionality have been deferred to a future version, or are incompletely covered in this 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:

• AllergyIntolerance : new codes needed for certainty?
• AllergyIntolerance : how to report 'no known allergies' of various flavors How should "No Known Allergies" be represented?
• Appointment : suitability of Appointment.priority values Values for Appointment.priority: how interoperable are they
• BodySite : suitability of this as Should it be an independent resource or a resource? datatype?
• CarePlan ClinicalImpression : 2 questions General Questions about usage use
• ClinicalImpression Clinical Reasoning : general usage Multiple questions about implementation and usage
• Composition : question about Is title being mandatory, different to type? and open questions about document signatures
• Invariants Condition : is there a replaceement for XPath? How should "No Known Problems" be represented?
• DataElement : question about relationship between DataElement and other resources Should DataElement, be rolled into StructureDefinition as a Logical Model?
• Markdown : which markdown flavor can we settle on, if any? Probable that will recommend/require CommonMark in release 4 - implementation consequences?
• DiagnosticReport Extensibility : relationship with Observation Do we need to support modifier extensions on extensions?
• RESTful API : question about using the PATCH operation Consequence of side effects in batches and transactions?
• RESTful API : what should we do about side-effects and Should servers maintain ids when processing transactions?
• RESTful API : Transaction integrity and introspection What are the documentation requirements around transaction integrity?
• Managing Resource Identification Identity : identifier policy rules? Mandating Identification practices for cross-system interoperability?
• Messaging Observation : what additional events Request for feedback on using the lastn operation and whether it should be defined? applied to other resources
• Operations : should it be possible Do we need a way to execute operations asynchronously?
• Patient : what effect linking/merging/unlinking should have on other functionality such as Should linking/merging affect the GET operation? RESTful API?
• Patient Profiling Resources : Comment Need feedback on MPI search query sought using system profiles
• Profiling JSON-LD format : Note about need for Need feedback about use of profiles on the JSON-LD format and it's usefulness
• References between Resources : Should inside out containment be allowed? Do we need to allow contained resources that reference the container?
• RiskAssessment Safety : General usage questions Request for comments about further development
• Search : how much should does text search need to be standardised? standardized?
• Search : Should additional rules about how _include works be made? Problems with which elements are marked as 'included in summary'
• Security : Using Feedback about signatures with on RESTful interfaces is a poorly understood area sought
• Subscription : Use with messaging is details still to be clarified resolved
• Workflow : several implementation questions