This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Supply FHIR Resource Proposal"
Jump to navigation
Jump to search
| Line 63: | Line 63: | ||
<!-- 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. --> | ||
| − | *Role: Supply ( | + | *Role: Supply (classCode=SPLY, moodCode=EVN) |
==Resource appropriateness== | ==Resource appropriateness== | ||
| Line 79: | Line 79: | ||
* Have the characteristics of high cohesion & low coupling – need to explore whether coupling is good some places, not elsewhere – layers from Bo’s document | * Have the characteristics of high cohesion & low coupling – need to explore whether coupling is good some places, not elsewhere – layers from Bo’s document | ||
--> | --> | ||
| − | Supplies in healthcare are necessary for the | + | Supplies in healthcare are necessary for the tracking of delivery of materials to the patient's room, dispensing of medicinal products, etc. |
==Expected implementations== | ==Expected implementations== | ||
<!-- 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) --> | ||
| − | + | Required for CCDA | |
==Content sources== | ==Content sources== | ||
| Line 123: | Line 123: | ||
*Lorraine Constable | *Lorraine Constable | ||
*Patrick Loyd | *Patrick Loyd | ||
| + | |||
| + | |||
| + | ==Issues== | ||
| + | # Need to decide whether this gets merged with MedicationDispense. If not, need to define scope to explicitly exclude that (both scope & RIM mapping) | ||
| + | # Need to expand the description a little bit. Is this only for "supply to patient" or does it include any transfer of material within healthcare? Can it include patient transport? If not, where is that handled? | ||
| + | # Need relationships identified. (Particularly confused by ImagingStudy) | ||
| + | # Should look at NCPDP, probably OpenEHR, jurisdictional specifications (e.g. Vision dispense for pan-Canadian claims) | ||
Revision as of 17:11, 12 June 2013
This page documents a Pending FHIR Resource Proposal
Contents
Supply
Owning committee name
Interested Work Groups
- Pharmacy
- Anatomic Pathology
- Clinical Genomics
- Imaging Integration
- Public Health and Emergency Response
FHIR Resource Development Project Insight ID
952
Scope of coverage
DEFINITION (SUPPLY): The supply resource covers information needed for the ordering and distribution of supplies within a healthcare facility or office.
Scope Challenge: Should MedicationDispense use the supply resource?
RIM scope
- Role: Supply (classCode=SPLY, moodCode=EVN)
Resource appropriateness
Supplies in healthcare are necessary for the tracking of delivery of materials to the patient's room, dispensing of medicinal products, etc.
Expected implementations
Required for CCDA
Content sources
- HL7 v3 Pharmacy Standard
- HL7 v2.x
- HL7 v3 Diet and Nutrition DAM
Resource Relationships
- Order
- DiagnosticOrder
- MedicationPrescription
- ImagingStudy
Timelines
- Vote by WG (Ready for ballot): July 2013
- Ballot: September 2013
gForge Users
- Lorraine Constable
- Patrick Loyd
Issues
- Need to decide whether this gets merged with MedicationDispense. If not, need to define scope to explicitly exclude that (both scope & RIM mapping)
- Need to expand the description a little bit. Is this only for "supply to patient" or does it include any transfer of material within healthcare? Can it include patient transport? If not, where is that handled?
- Need relationships identified. (Particularly confused by ImagingStudy)
- Should look at NCPDP, probably OpenEHR, jurisdictional specifications (e.g. Vision dispense for pan-Canadian claims)
