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

Difference between revisions of "OrganizationAffiliation FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
(Created page with "{{subst::Template:FHIR Resource Proposal}}")
 
Line 13: Line 13:
  
  
=PutProposedResourceNameHere=
+
=OrganizationAffiliation=
  
<!-- Resource names should meet the following characteristics:
+
==Patient Administration==
* Lower camel case
 
* U.S. English
 
* Domain-friendly
 
* Short
 
* Clear
 
* Unique
 
* Avoid non-universal abbreviations (e.g. URL would be ok)
 
* Be expressed as a noun
 
* Be consistent with other similar resources
 
-->
 
 
 
==Owning committee name==
 
  
 
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the resources. -->
 
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the resources. -->
[[YourCommitteeName]]
+
[http://wiki.hl7.org/index.php?title=Patient_Administration Patient Administration]
 
==Committee Approval Date:==
 
==Committee Approval Date:==
 
<i>Please enter the date that the committee approved this Resource proposal</i>
 
<i>Please enter the date that the committee approved this Resource proposal</i>
Line 36: Line 24:
 
==Contributing or Reviewing Work Groups==
 
==Contributing or Reviewing Work Groups==
  
<!-- Additional work groups that may have an interest in contributing to, or reviewing  the content of the resource (optional) -->
+
* "None"
* Work Group Name
 
* or link
 
* or "None"
 
  
 
==FHIR Resource Development Project Insight ID==
 
==FHIR Resource Development Project Insight ID==
Line 47: Line 32:
 
==Scope of coverage==
 
==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%"
+
(need to differentiate from Organization)
 
+
A formally or informally recognized relationship between organizations for the purpose of achieving some form of collective action. Includes membership with a Health Information exchange, a separate physician organization, or any other relationships where the entities are separate business entities.
Scope should consider numerous aspects of breadth of scope, including:
+
-
* Subject: Human vs. non-human vs. non-patient (e.g. lab bench medicine)
+
This resource may be used to identify inter-organization relationships when two different organizations have separate parent organizations. This resource should not be used when the affiliates are owned by a single organization.  
* 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==

Revision as of 15:50, 7 February 2017



OrganizationAffiliation

Patient Administration

Patient Administration

Committee Approval Date:

Please enter the date that the committee approved this Resource proposal

Contributing or Reviewing Work Groups

  • "None"

FHIR Resource Development Project Insight ID

Scope of coverage

(need to differentiate from Organization) A formally or informally recognized relationship between organizations for the purpose of achieving some form of collective action. Includes membership with a Health Information exchange, a separate physician organization, or any other relationships where the entities are separate business entities. - This resource may be used to identify inter-organization relationships when two different organizations have separate parent organizations. This resource should not be used when the affiliates are owned by a single organization.


RIM scope

Resource appropriateness

Expected implementations

Content sources

Example Scenarios

Resource Relationships

Timelines

gForge Users

When Resource Proposal Is Complete

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