This wiki has undergone a migration to Confluence found Here
Difference between revisions of "DeviceAlert FHIR Resource Proposal"
Jump to navigation
Jump to search
| Line 58: | Line 58: | ||
<!-- Identify the formal RIM mapping for the root concept of the resource. The expectation is that the RIM mapping will be sufficiently precise so as to not overlap with any other resource definition. --> | <!-- Identify the formal RIM mapping for the root concept of the resource. The expectation is that the RIM mapping will be sufficiently precise so as to not overlap with any other resource definition. --> | ||
| + | TBD | ||
==Resource appropriateness== | ==Resource appropriateness== | ||
Revision as of 18:26, 3 October 2014
This page documents a Pending FHIR Resource Proposal
Contents
- 1 DeviceAlert
- 1.1 Owning committee name
- 1.2 Contributing or Reviewing Work Groups
- 1.3 FHIR Resource Development Project Insight ID
- 1.4 Scope of coverage
- 1.5 RIM scope
- 1.6 Resource appropriateness
- 1.7 Expected implementations
- 1.8 Content sources
- 1.9 Example Scenarios
- 1.10 Resource Relationships
- 1.11 Timelines
- 1.12 gForge Users
DeviceAlert
Owning committee name
Contributing or Reviewing Work Groups
FHIR Resource Development Project Insight ID
TBD
Scope of coverage
RIM scope
TBD
