This wiki has undergone a migration to Confluence found Here

Difference between revisions of "Accout FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
(Blanked the page)
Line 1: Line 1:
<div class="messagebox cleanup metadata">
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
<div style="background:#F0F0F0">
This page documents a [[:category:Pending FHIR Resource Proposal|Pending]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]]
[[Category:FHIR Resource Proposal]]
[[Category:Pending FHIR Resource Proposal]]
==Owning committee name==
[[Patient Administration]]
==Contributing or Reviewing Work Groups==
[[Financial Management]]
==FHIR Resource Development Project Insight ID==
Project Insight? 1102
(Account is not part of this project as yet)
<!-- Please specify the id of your work group’s PSS for doing FHIR work.  (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: -->
==Scope of coverage==
<!-- 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%"
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.
The Account resource is used to track patient billing accounts.
It does not cover the actual transactions, just balances, insurance coverage (via reference), currency and status.
==RIM scope==
<!-- Identify the formal RIM mapping for the root concept of the resource.  The expectation is that the RIM mapping will be sufficiently precise so as to not overlap with any other resource definition. -->
FIAB_RM010000UV02 (Patient Account Event)
==Resource appropriateness==
<!-- Does the resource meet the following characteristics?
* 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
* 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
Tracking Financial information is vital in Patient Administration and Finance systems in most Healthcare Organizations. This resource provides the base point to track.
==Expected implementations==
* Any solution that requires tracking billing information
==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
Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? -->
Existing normative V3 and V2 specifications
==Example Scenarios==
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this resource.  They should demonstrate the full scope of the resource and allow exercising of the resources capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) -->
* Tracking Balances for Patient Accounts in a General Practice Clinic or Hospital
* Tracking Funding between a govt. funded project and an Organization
* Tracking Funding between 2 Organizations where services are provided by one org to another
==Resource Relationships==
<!-- What are the resources do you expect will reference this resource and in what context?
What resources do you expect this resource reference and in what context?
Note: These may be existing resources or "expected" resource
Reference to resources is really only relevant at the "same or higher level" (Bo – fix this wording)
* [ Patient]
* [ Organization]
* [ Location]
* [ Practitioner]
Potentially used by (need to determine resource)
* Insurer/Coverage
* Guarantor
The Account will be referenced by:
* Encounter
* EpisodeOfCare
* BillableItem (future resource)
* HealthcareService
* Device
<!-- Indicate the target date for having the resource complete from a committee perspective and ready for vetting and voting -->
We have built a draft placeholder for this resource, and working with the Finance WG to refine it during the 2.1/3.0 timeline.
==gForge Users==
<!-- Identify the userids who will require commit access to gForge to maintain the resource.  (Ensure all users have registered for gForge.) -->

Latest revision as of 21:06, 1 December 2015