Difference between revisions of "VisionPrescription FHIR Resource Proposal"
Paul Knapp (talk | contribs) (Created page with "=VisionPrescription= <!-- Resource names should meet the following characteristics: * Lower camel case * U.S. English * Domain-friendly * Short * Clear * Unique * Avoid non-u...") |
Paul Knapp (talk | contribs) |
||
| Line 1: | Line 1: | ||
| + | |||
| + | <div class="messagebox cleanup metadata"> | ||
| + | <div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div> | ||
| + | <div style="background:#F0F0F0"> | ||
| + | This page documents a [[:category:Pending FHIR Resource Proposal|Pending]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]] | ||
| + | </div> | ||
| + | </div> | ||
| + | [[Category:FHIR Resource Proposal]] | ||
| + | [[Category:Pending FHIR Resource Proposal]] | ||
| + | |||
=VisionPrescription= | =VisionPrescription= | ||
Revision as of 16:54, 29 October 2014
This page documents a Pending FHIR Resource Proposal
Contents
- 1 VisionPrescription
- 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
VisionPrescription
Owning committee name
Financial Management as custodian
Contributing or Reviewing Work Groups
- Patient Administration
FHIR Resource Development Project Insight ID
994
Scope of coverage
Prescription (or Ordering) of Vision products and services Humans and Animals across All Healthcare Disciplines in All Care Settings and All Regions. The VisionPrescription resource indicates what was authorized but is not, in itself, a request for action. To request fulfilment of a prescription use the Order resource to initiate the request.
RIM scope
???
Resource appropriateness
Vision Prescription is one of the core steps of use of Vision products, another being Dispensing (or Supply). In many settings the steps are performed by separate people, and are frequently recorded by separate software systems. Prescription records are a core part of knowing what products a patient is supposed to receive - having a standard format for this is essential. There is a well established set of attributes that are always required.
Expected implementations
This is a key resource expected by most Healthcare billing implementations where Health care products and services are provided.
Content sources
Existing normative V3 and V2 specifications, Canadian Specifications, X12
Example Scenarios
Resource Relationships
Refers to Patient, Practitioner, Organization. Is referred to by a VisionClaim. Perhaps in the future will be referred by an Order for the actual fulfillment of the prescription and a VisionDispense for the result of the fulfillment.
Timelines
Ready for DSTU 2
gForge Users
paulknapp
