This wiki has undergone a migration to Confluence found Here
Difference between revisions of "ReferralRequest FHIR Resource Proposal"
Jump to navigation
Jump to search
StephenChu (talk | contribs) |
StephenChu (talk | contribs) |
||
| Line 54: | Line 54: | ||
==Scope of coverage== | ==Scope of coverage== | ||
| + | <br> | ||
| + | * In scope: | ||
| + | |||
| + | : - Patients (especially those with complex health conditions) are care for by multi-disciplinary health care teams. They may also be transitioned between different health care settings (e.g. from acute care to rehabilitation or long term care/skilled nursing facilities). The referral and transition of care processes with appropriate supporting documents are required to initiate and complete these processes | ||
| + | |||
| + | : - The referral and transition of care resources will be designed to enable exchange of crucial administrative and clinical information to support these processes | ||
| + | |||
| + | : - Administrative data are likely to include: Patient details, provider and provider organisation details (and others to be identified) | ||
| + | |||
| + | : - It is not uncommon for "care plan" or components of care plan to be included in a referral or transition of care information package | ||
| + | |||
| + | |||
| + | * Out of scope: | ||
| + | |||
| + | : - While it pathology and imaging studies requests are increasingly considered as a specialization of referral, until there is industry wide agreement on this thinking, such requests should use the Pathology and Imaging resources | ||
| + | |||
| + | |||
| + | <br> | ||
<!-- Define the full scope of coverage for the resource. The scope must be clearly delineated such that it does not overlap with any other existing or expected resource. The scope will be used to govern "what is the set of potential applications to consider when evaluating what elements are 'core' – i.e. in the 80%" | <!-- Define the full scope of coverage for the resource. The scope must be clearly delineated such that it does not overlap with any other existing or expected resource. The scope will be used to govern "what is the set of potential applications to consider when evaluating what elements are 'core' – i.e. in the 80%" | ||
Revision as of 00:49, 15 May 2014
This page documents a Pending FHIR Resource Proposal
Contents
- 1 Referral
- 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
Referral
Owning committee name
Contributing or Reviewing Work Groups
- Workgroup: Patient Care
- Project wiki link: Referral and Transition/Transfer of Care
FHIR Resource Development Project Insight ID
Pending
Scope of coverage
- In scope:
- - Patients (especially those with complex health conditions) are care for by multi-disciplinary health care teams. They may also be transitioned between different health care settings (e.g. from acute care to rehabilitation or long term care/skilled nursing facilities). The referral and transition of care processes with appropriate supporting documents are required to initiate and complete these processes
- - The referral and transition of care resources will be designed to enable exchange of crucial administrative and clinical information to support these processes
- - Administrative data are likely to include: Patient details, provider and provider organisation details (and others to be identified)
- - It is not uncommon for "care plan" or components of care plan to be included in a referral or transition of care information package
- Out of scope:
- - While it pathology and imaging studies requests are increasingly considered as a specialization of referral, until there is industry wide agreement on this thinking, such requests should use the Pathology and Imaging resources
