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 95: | Line 95: | ||
*HL7 v2.x | *HL7 v2.x | ||
*HL7 v3 Diet and Nutrition DAM | *HL7 v3 Diet and Nutrition DAM | ||
| + | |||
| + | ==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 130: | Line 134: | ||
# Need relationships identified. (Particularly confused by ImagingStudy) | # Need relationships identified. (Particularly confused by ImagingStudy) | ||
# Should look at NCPDP, probably OpenEHR, jurisdictional specifications (e.g. Vision dispense for pan-Canadian claims) | # Should look at NCPDP, probably OpenEHR, jurisdictional specifications (e.g. Vision dispense for pan-Canadian claims) | ||
| + | # Need example scenarios | ||
Revision as of 18:13, 12 June 2013
This page documents a Pending FHIR Resource Proposal
Contents
- 1 Supply
- 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
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
Example Scenarios
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)
- Need example scenarios
