This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "HealthcareService FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
(Created page with " <div class="messagebox cleanup metadata"> <div style="float: left;">35px| </div> <div style="background:#F0F0F0"> This page documents a :category...")
 
Line 52: Line 52:
  
 
==Example Scenarios==
 
==Example Scenarios==
 +
A Government Body that exposes a directory of service data (e.g. http://www.nhsd.com.au/) would provides 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.
  
 
==Resource Relationships==
 
==Resource Relationships==

Revision as of 18:02, 6 May 2014



HealthcareService

Owning committee name

Patient Administration

Contributing or Reviewing Work Groups

  • "None"

FHIR Resource Development Project Insight ID

pending

Scope of coverage

HealthcareService resources are used to provide detailed information about a healthcare service that is provided by an organization at a location (which may be virtual), who can perform the service and what are its typical characteristics.


RIM scope

?


Resource appropriateness

This resource contains the content that is often exposed on an organizations website to help consumers (and their personal care providers as a proxy) to locate appropriate services which meet their needs.

Currently the extraction/update 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 used by Organizations wanting to expose their service information to other systems to facilitate the discovery process. National Directory Services would likely aggregate this information and expose for consumer apps, provider apps and also integration into mainstream healthcare systems to keep their internal "black book" of favorite providers up to date.

Patient Administration Systems could access these resources to ensure that their list of external providers services remains up to date.


Content sources

The sources for information related to this service we will be consulting with 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 provides 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.

Resource Relationships

This resource is expected to have references to Location, Organization, Practitioner.


Timelines

We expect that this resource will be ready for inclusion in the next Ballot (expecting September 2014).


gForge Users

brian_pos ewoutkramer