Difference between revisions of "ProductPlan Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
Line 29: Line 29:
 
ProductPlan describes a health insurance offering comprised of a list of covered benefits (i.e. the product), costs associated with those benefits (i.e. the plan), and additional information about the offering, such as who it is owned and administered by, a coverage area, contact information, etc.  
 
ProductPlan describes a health insurance offering comprised of a list of covered benefits (i.e. the product), costs associated with those benefits (i.e. the plan), and additional information about the offering, such as who it is owned and administered by, a coverage area, contact information, etc.  
  
<!-- 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%"
+
The ProductPlan does not represent the details for a specific patient, that is the Coverage resource.
 
 
Scope should consider numerous aspects of breadth of scope, including:
 
* Subject: Human vs. non-human vs. non-patient (e.g. lab bench medicine)
 
* Disciplines: Environmental Health, Palliative, Respiratory, Psychology, Maternity, Clinical Research
 
* Delivery environment (Community, Geriatric, Home care, Emergency, Inpatient, Intensive, Neonatal, Pediatric, Primary)
 
* Locale: Country, region
 
 
 
As a rule, resources should encompass all of these aspects.
 
-->
 
  
 
==RIM scope==
 
==RIM scope==
Line 44: Line 35:
  
 
==Resource appropriateness==
 
==Resource appropriateness==
 +
A catalog to discover providers that provide specific insurance products is useful for both patients/consumers, and also for providers to verify details.
  
<!-- Does the resource meet the following characteristics?
+
The information from the catalog will also be able to be utilized in Patient Coverage resources.
 
 
Must
 
* Represents a well understood, "important" concept in the business of healthcare
 
* Represents a concept expected to be tracked with distinct, reliable, unique ids
 
* Reasonable for the resource to be independently created, queried and maintained
 
 
 
Should
 
* Declared interest in need for standardization of data exchange</span>
 
* Resource is expected to contain an appropriate number of "core" (non-extension) data elements (in most cases, somewhere in the range of 20-50)
 
* Have the characteristics of high cohesion & low coupling – need to explore whether coupling is good some places, not elsewhere – layers from Bo’s document
 
-->
 
  
 
==Expected implementations==
 
==Expected implementations==
 
The ONC has indicated that they desire to create a service that uses this capability where they will be distributing aggregated healthcare directory data from a central service to Organizations for local usage (based on a specific data usage agreement)
 
The ONC has indicated that they desire to create a service that uses this capability where they will be distributing aggregated healthcare directory data from a central service to Organizations for local usage (based on a specific data usage agreement)
 
<!--Key resources are justified by CCDA, for resources not deemed "key", what interest is there by implementers in using this particular resource. Provide named implementations if possible - ideally provide multiple independent implementations. -->
 
  
 
==Content sources==
 
==Content sources==
 
 
<!-- List all of the specifications (beyond those in the "standard" (FHIR_Design_Requirements_Sources) list of source specifications) that you’re planning to consult
 
<!-- List all of the specifications (beyond those in the "standard" (FHIR_Design_Requirements_Sources) list of source specifications) that you’re planning to consult
  

Revision as of 11:32, 14 May 2018

ProductPlan

Owning work group name

Patient Administration

Committee Approval Date:

Contributing or Reviewing Work Groups

  • Financial Management
  • Seeking other interested workgroups

FHIR Resource Development Project Insight ID

1345

Scope of coverage

A product is a discrete package of health insurance coverage benefits that are offered under a particular network type. A given payer’s products typically differ by network type and/or coverage benefits. A plan pairs the health insurance coverage benefits under a product with the particular cost sharing structure offered to a consumer. A given product may comprise multiple plans.

ProductPlan describes a health insurance offering comprised of a list of covered benefits (i.e. the product), costs associated with those benefits (i.e. the plan), and additional information about the offering, such as who it is owned and administered by, a coverage area, contact information, etc.

The ProductPlan does not represent the details for a specific patient, that is the Coverage resource.

RIM scope

unknown

Resource appropriateness

A catalog to discover providers that provide specific insurance products is useful for both patients/consumers, and also for providers to verify details.

The information from the catalog will also be able to be utilized in Patient Coverage resources.

Expected implementations

The ONC has indicated that they desire to create a service that uses this capability where they will be distributing aggregated healthcare directory data from a central service to Organizations for local usage (based on a specific data usage agreement)

Content sources

Example Scenarios

  • Centralized Healthcare Directory service
  • Distributed/Federated Provider Directory service
  • Aggregated Directory Service

Resource Relationships

Reference(any) - Our initial requirements are needed against:

  • Organization
  • Location

We do not currently expect other resources to specifically reference ProductPlan

Timelines

Sept Ballot 2018 - draft was in Jan 2018 Comment ballot

gForge Users

  • brian_pos
  • Cooper Thompson
  • Andrew Torres

When Resource Proposal Is Complete

When you have completed your proposal, please send an email to FMGcontact@HL7.org

FMG Notes