Difference between revisions of "HealthcareService FHIR Resource Proposal"
| (9 intermediate revisions by one other user not shown) | |||
| Line 3: | Line 3: | ||
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div> | <div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div> | ||
<div style="background:#F0F0F0"> | <div style="background:#F0F0F0"> | ||
| − | This page documents a [[:category: | + | This page documents a [[:category:Approved FHIR Resource Proposal|Approved]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]] |
</div> | </div> | ||
</div> | </div> | ||
[[Category:FHIR Resource Proposal]] | [[Category:FHIR Resource Proposal]] | ||
| − | [[Category: | + | [[Category:Approved FHIR Resource Proposal]] |
| Line 42: | Line 42: | ||
==Expected implementations== | ==Expected implementations== | ||
| − | This resource is likely to be implemented by applications with Service Directories: | + | This resource is likely to be implemented by applications with Service Directories such as: |
| − | |||
| − | |||
* Patient Administration Systems | * Patient Administration Systems | ||
| + | * Web portal(s) exposing service information | ||
* National/Regional/HIE Service Directory Systems | * National/Regional/HIE Service Directory Systems | ||
==Content sources== | ==Content sources== | ||
| − | + | We will be referring to the existing OMG ServD Standard, and the HL7 v2 and v3 messages and models. | |
| − | |||
==Example Scenarios== | ==Example Scenarios== | ||
| − | A Government Body that exposes a directory of service data (e.g. http://www.nhsd.com.au/) would | + | A Government Body that exposes a directory of service data (e.g. http://www.nhsd.com.au/) would provide its service information publicly. |
This would be accessible both as a website, and also as a service that can be interrogated by "apps" to re-present this information for specific audiences (e.g. http://www.betterhealth.vic.gov.au/) | This would be accessible both as a website, and also as a service that can be interrogated by "apps" to re-present this information for specific audiences (e.g. http://www.betterhealth.vic.gov.au/) | ||
| Line 60: | Line 58: | ||
A hospital wants to keep its internal list of organizations that it regularly sends referral information to up to date with the hours and service offerings up to date without having to manually update and enter their information. | A hospital wants to keep its internal list of organizations that it regularly sends referral information to up to date with the hours and service offerings up to date without having to manually update and enter their information. | ||
| − | A | + | A consumer is able to locate a service that has specific eligibility requirements which searching. Such as covered by Health Insurance, or Organization (e.g VA covered) |
==Resource Relationships== | ==Resource Relationships== | ||
This resource is expected to have references to Location, Organization, Practitioner. | This resource is expected to have references to Location, Organization, Practitioner. | ||
| + | Other relationships may include: Appointment, Encounter, Coverage, CarePlan. | ||
==Timelines== | ==Timelines== | ||
We expect that this resource will be ready for inclusion in the next Ballot (expecting September 2014). | We expect that this resource will be ready for inclusion in the next Ballot (expecting September 2014). | ||
| − | |||
==gForge Users== | ==gForge Users== | ||
brian_pos | brian_pos | ||
ewoutkramer | ewoutkramer | ||
Latest revision as of 21:34, 5 December 2014
This page documents a Approved FHIR Resource Proposal
Contents
- 1 HealthcareService
- 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
HealthcareService
Owning committee name
Contributing or Reviewing Work Groups
FHIR Resource Development Project Insight ID
pending
Scope of coverage
A HealthcareService Resource provides detailed information about a healthcare service that is provided by an organization at a location (which may be virtual), and its typical characteristics.
Note: The Term "Service" in this context does not refer to a SOA/web service or other IT related service.
RIM scope
V3 V2 AIS?
Resource appropriateness
This resource is used to help consumers and providers locate appropriate services which meet care needs.
Currently the exchange of this information between systems is manual or proprietary and the desire for this to be standardized and easier to expose is highly desirable.
Expected implementations
This resource is likely to be implemented by applications with Service Directories such as:
- Patient Administration Systems
- Web portal(s) exposing service information
- National/Regional/HIE Service Directory Systems
Content sources
We will be referring to the existing OMG ServD Standard, and the HL7 v2 and v3 messages and models.
Example Scenarios
A Government Body that exposes a directory of service data (e.g. http://www.nhsd.com.au/) would provide its service information publicly. This would be accessible both as a website, and also as a service that can be interrogated by "apps" to re-present this information for specific audiences (e.g. http://www.betterhealth.vic.gov.au/)
A Healthcare organization wanting to publish their service data for their consumers (e.g. https://healthy.kaiserpermanente.org/health/care/consumer/locate-our-services/doctors-and-locations/)
A hospital wants to keep its internal list of organizations that it regularly sends referral information to up to date with the hours and service offerings up to date without having to manually update and enter their information.
A consumer is able to locate a service that has specific eligibility requirements which searching. Such as covered by Health Insurance, or Organization (e.g VA covered)
Resource Relationships
This resource is expected to have references to Location, Organization, Practitioner.
Other relationships may include: Appointment, Encounter, Coverage, CarePlan.
Timelines
We expect that this resource will be ready for inclusion in the next Ballot (expecting September 2014).
gForge Users
brian_pos ewoutkramer
