Difference between revisions of "ProductPlan Resource Proposal"
Line 19: | Line 19: | ||
==Contributing or Reviewing Work Groups== | ==Contributing or Reviewing Work Groups== | ||
* Financial Management | * Financial Management | ||
− | * Seeking interested workgroups | + | * Seeking other interested workgroups |
==FHIR Resource Development Project Insight ID== | ==FHIR Resource Development Project Insight ID== |
Revision as of 11:28, 14 May 2018
Contents
- 1 ProductPlan
- 1.1 Owning work group name
- 1.2 Committee Approval Date:
- 1.3 Contributing or Reviewing Work Groups
- 1.4 FHIR Resource Development Project Insight ID
- 1.5 Scope of coverage
- 1.6 RIM scope
- 1.7 Resource appropriateness
- 1.8 Expected implementations
- 1.9 Content sources
- 1.10 Example Scenarios
- 1.11 Resource Relationships
- 1.12 Timelines
- 1.13 gForge Users
- 1.14 When Resource Proposal Is Complete
- 1.15 FMG Notes
ProductPlan
Owning work group name
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.
RIM scope
unknown
Resource appropriateness
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