This wiki has undergone a migration to Confluence found Here

Difference between revisions of "Organization FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
Line 1: Line 1:
 
 
<div class="messagebox cleanup metadata">
 
<div class="messagebox cleanup metadata">
 
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
 
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
Line 35: Line 34:
  
 
<!-- Additional work groups that may have an interest in contributing to, or reviewing  the content of the resource (optional) -->
 
<!-- Additional work groups that may have an interest in contributing to, or reviewing  the content of the resource (optional) -->
* "None"
+
None
  
 
==FHIR Resource Development Project Insight ID==
 
==FHIR Resource Development Project Insight ID==
  
 
<!-- 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: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc -->
 
<!-- 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: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc -->
*925
+
925
  
 
==Scope of coverage==
 
==Scope of coverage==
Line 54: Line 53:
 
As a rule, resources should encompass all of these aspects.
 
As a rule, resources should encompass all of these aspects.
 
  -->
 
  -->
A formally or informally recognized grouping of people or organizations formed for the purpose of achieving some form of collective action. Includes companies, institutions, corporations, departments, community groups, healthcare practice groups, etc.<br/>
+
The resource cover formally or informally recognized grouping of people or organizations formed for the purpose of achieving some form of collective action. Includes companies, institutions, corporations, departments, community groups, healthcare practice groups, etc.
<br/>
 
The resource name as it appears in a RESTful URL is /organization/
 
  
 
==RIM scope==
 
==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. -->
 
<!-- 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. -->
 
Organization
 
Organization
  
 
==Resource appropriateness==
 
==Resource appropriateness==
 
+
Many care-related processes are done by people acting on behalf of organizations. Where this is the case, the organization needs to be tracked. Organizations can be identified using numbers assigned by national registries.
 
<!-- Does the resource meet the following characteristics?
 
<!-- Does the resource meet the following characteristics?
  
Line 79: Line 75:
  
 
==Expected implementations==
 
==Expected implementations==
 +
Most, if not all, hospital information systems.
  
 
<!--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. -->
 
<!--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==
 
+
None beyond the standard list.
 
<!-- 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
  
Line 93: Line 90:
  
 
==Resource Relationships==
 
==Resource Relationships==
 
+
Will be referenced, amongst others, by Practitioner (scoped by the organization) and Location (owned/administered by the organization)
 
<!-- What are the resources do you expect will reference this resource and in what context?
 
<!-- What are the resources do you expect will reference this resource and in what context?
  
Line 104: Line 101:
  
 
==Timelines==
 
==Timelines==
 
+
Expected to be ready for the sept 2013 DSTU ballot.
 
<!-- Indicate the target date for having the resource complete from a committee perspective and ready for vetting and voting -->
 
<!-- Indicate the target date for having the resource complete from a committee perspective and ready for vetting and voting -->
  
 
==gForge Users==
 
==gForge Users==
 
+
ewoutkramer
 
<!-- Identify the userids who will require commit access to gForge to maintain the resource.  (Ensure all users have registered for gForge.) -->
 
<!-- Identify the userids who will require commit access to gForge to maintain the resource.  (Ensure all users have registered for gForge.) -->

Revision as of 09:21, 5 June 2013



Organization

Owning committee name

Patient_Administration

Contributing or Reviewing Work Groups

None

FHIR Resource Development Project Insight ID

925

Scope of coverage

The resource cover formally or informally recognized grouping of people or organizations formed for the purpose of achieving some form of collective action. Includes companies, institutions, corporations, departments, community groups, healthcare practice groups, etc.

RIM scope

Organization

Resource appropriateness

Many care-related processes are done by people acting on behalf of organizations. Where this is the case, the organization needs to be tracked. Organizations can be identified using numbers assigned by national registries.

Expected implementations

Most, if not all, hospital information systems.


Content sources

None beyond the standard list.

Example Scenarios

Resource Relationships

Will be referenced, amongst others, by Practitioner (scoped by the organization) and Location (owned/administered by the organization)

Timelines

Expected to be ready for the sept 2013 DSTU ballot.

gForge Users

ewoutkramer