Difference between revisions of "Other FHIR Resource Proposal"
(2 intermediate revisions by one other user not shown) | |||
Line 2: | Line 2: | ||
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div> | <div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div> | ||
<div style="background:#F0F0F0"> | <div style="background:#F0F0F0"> | ||
− | This page documents | + | This page documents an [[:category:Approved FHIR Resource Proposal|Approved]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]] |
</div> | </div> | ||
</div> | </div> | ||
[[Category:FHIR Resource Proposal]] | [[Category:FHIR Resource Proposal]] | ||
− | [[Category: | + | [[Category:Approved FHIR Resource Proposal]] |
Line 53: | Line 53: | ||
As a rule, resources should encompass all of these aspects. | As a rule, resources should encompass all of these aspects. | ||
--> | --> | ||
+ | This is <b>not</b> a typical resource in that it doesn't have a bounded set of semantics. | ||
+ | |||
The Other resource is intended to cover all use-cases not met by HL7-defined resources. This includes resources that HL7 intends to create as well as those that are outside the scope of what HL7 will define. The scope of this resource will evolve as additional resources are defined. | The Other resource is intended to cover all use-cases not met by HL7-defined resources. This includes resources that HL7 intends to create as well as those that are outside the scope of what HL7 will define. The scope of this resource will evolve as additional resources are defined. | ||
+ | |||
+ | This resource provides a mechanism for implementers to implement "custom" resources while still falling within the bounds of FHIR conformance, avoiding issues with collisions and ensuring that the meaning of elements within the resource remains discoverable. | ||
+ | |||
+ | The time-frame for migration from the Other resource to official HL7-defined resources is up to implementers. | ||
==RIM scope== | ==RIM scope== |
Latest revision as of 05:46, 22 May 2014
Contents
- 1 Other
- 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
Other
Owning committee name
FHIR Core Team
Contributing or Reviewing Work Groups
- None
FHIR Resource Development Project Insight ID
Pending
Scope of coverage
This is not a typical resource in that it doesn't have a bounded set of semantics.
The Other resource is intended to cover all use-cases not met by HL7-defined resources. This includes resources that HL7 intends to create as well as those that are outside the scope of what HL7 will define. The scope of this resource will evolve as additional resources are defined.
This resource provides a mechanism for implementers to implement "custom" resources while still falling within the bounds of FHIR conformance, avoiding issues with collisions and ensuring that the meaning of elements within the resource remains discoverable.
The time-frame for migration from the Other resource to official HL7-defined resources is up to implementers.
RIM scope
InfrastructureRoot
Resource appropriateness
The primary purpose of this resource is to provide a safety valve for implementers where they have requirements not met by the existing FHIR specification. Extensibility is a key part of the FHIR methodology, including at the resource level. The is resource is different from others in that it isn't linked to a single concept. Instead, the concept represented by the resource is defined by an HL7-specific terminology (extensible for local use).
Expected implementations
The need for additional as-yet undefined resources is well recognized. Existing implementers are already encountering it.
Content sources
The initial vocabulary for Other resource types will be taken from the set of candidate resources identified on the wiki
Example Scenarios
The set of examples will need to be updated over time as new resources are defined.
- Referral
- UML diagram
Resource Relationships
- Link to Patient (as subject) and Practitioner (as author)
- Can link to any other resources via extensions
Timelines
Included in initial DSTU
gForge Users
N/A