Difference between revisions of "OrderResponse FHIR Resource Proposal"
| Line 47: | Line 47: | ||
--> | --> | ||
| − | The response to an order indicates the outcome of processing the order itself - whether it was accepted or rejected, or is still in process. The order response resource does not itself convey or represent information that arises as a result of performing the actual order, but it may have references to other resources that do have this information | + | The response to an order indicates the outcome of processing the order itself - whether it was accepted or rejected, or is still in process. The order response resource does not itself convey or represent information that arises as a result of performing the actual order, but it may have references to other resources that do have this information in order to link between the original order and its outcome. |
There may be multiple responses for a given order. For some requests, a responding system may issue a sequence of responses, where each response replaces previous responses as the original order is processed/performed. In these cases, each response should have the same logical identity, and the multiple responses are different versions of the same overall response. | There may be multiple responses for a given order. For some requests, a responding system may issue a sequence of responses, where each response replaces previous responses as the original order is processed/performed. In these cases, each response should have the same logical identity, and the multiple responses are different versions of the same overall response. | ||
| Line 56: | Line 56: | ||
<!-- 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. --> | ||
| − | ActClass = | + | ActClass = ACTN |
| − | MoodCode = | + | MoodCode = EVN |
==Resource appropriateness== | ==Resource appropriateness== | ||
| Line 74: | Line 74: | ||
--> | --> | ||
| − | + | The general pattern of request/response is essential for satisfying many workflow use-cases. The concept is supported by the EVN and ORC segments in R2 and by the ControlAct response wrappers in v3. | |
==Expected implementations== | ==Expected implementations== | ||
| Line 80: | Line 80: | ||
<!-- For resources not deemed "key", what interest is there by implementers in using this particular resource. (Should ideally have multiple independent implementations) --> | <!-- For resources not deemed "key", what interest is there by implementers in using this particular resource. (Should ideally have multiple independent implementations) --> | ||
| − | + | Used in some queries, pharmacy & lab fulfillment and other workflow scenarios | |
==Content sources== | ==Content sources== | ||
| Line 89: | Line 89: | ||
| − | + | *HL7 v2.x (ORC, EVN) | |
| − | *HL7 v2.x | + | *HL7 v3 (Control Act response wrappers) |
| − | *HL7 | + | *OpenEHR? |
| − | * | ||
| + | |||
| + | ==Example Scenarios== | ||
| + | |||
| + | <!-- Provide a listing of the types of scenarios to be represented in the examples produced for this resource. They should demonstrate the full scope of the resource and allow exercising of the resources capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) --> | ||
==Resource Relationships== | ==Resource Relationships== | ||
| Line 107: | Line 110: | ||
*Order | *Order | ||
*DiagnosticOrder | *DiagnosticOrder | ||
| + | *MedicationDispense | ||
| + | *MedicationPrescription | ||
*Specimen | *Specimen | ||
*Substance | *Substance | ||
| Line 124: | Line 129: | ||
*Patrick Loyd | *Patrick Loyd | ||
*Lorraine Constable | *Lorraine Constable | ||
| + | |||
| + | ==Issues== | ||
| + | * Modified RIM mapping and a few other things | ||
| + | * Need example scenarios | ||
Revision as of 13:55, 14 June 2013
This page documents a Pending FHIR Resource Proposal
Contents
- 1 Order
- 1.1 Owning committee name
- 1.2 Interested 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
- 1.13 Issues
Order
Owning committee name
FHIR Core Team But: OO will have eventual responsibility and has filled out the paperwork
Interested Work Groups
- Anatomic Pathology
- Clinical Genomics
- Imaging Integration
- Public Health and Emergency Response
- Pharmacy
FHIR Resource Development Project Insight ID
<not sure - this is a core team resource - what is the project insight ID for that?> 952
Scope of coverage
The response to an order indicates the outcome of processing the order itself - whether it was accepted or rejected, or is still in process. The order response resource does not itself convey or represent information that arises as a result of performing the actual order, but it may have references to other resources that do have this information in order to link between the original order and its outcome.
There may be multiple responses for a given order. For some requests, a responding system may issue a sequence of responses, where each response replaces previous responses as the original order is processed/performed. In these cases, each response should have the same logical identity, and the multiple responses are different versions of the same overall response.
If there are multiple systems responding to the request, or if there request may have multiple different responses, then the different logical responses should have different logical ids.
RIM scope
ActClass = ACTN MoodCode = EVN
Resource appropriateness
The general pattern of request/response is essential for satisfying many workflow use-cases. The concept is supported by the EVN and ORC segments in R2 and by the ControlAct response wrappers in v3.
Expected implementations
Used in some queries, pharmacy & lab fulfillment and other workflow scenarios
Content sources
- HL7 v2.x (ORC, EVN)
- HL7 v3 (Control Act response wrappers)
- OpenEHR?
Example Scenarios
Resource Relationships
- Order
- DiagnosticOrder
- MedicationDispense
- MedicationPrescription
- Specimen
- Substance
- Supply
- ImagingStudy
Timelines
- Vote by WG (Ready for ballot): July 2013
- Ballot: September 2013
gForge Users
- Patrick Loyd
- Lorraine Constable
Issues
- Modified RIM mapping and a few other things
- Need example scenarios
