This wiki has undergone a migration to Confluence found Here

Difference between revisions of "Group FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
(Created page with "{{subst::Template:FHIR Resource Proposal}}")
 
 
(4 intermediate revisions by 2 users not shown)
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>
 
<div style="background:#F0F0F0">
 
<div style="background:#F0F0F0">
This page documents a [[:category:Pending FHIR Resource Proposal|Pending]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]]
+
This page documents an [[:category:Approved FHIR Resource Proposal|Approved]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]]
 
</div>
 
</div>
 
</div>
 
</div>
 
[[Category:FHIR Resource Proposal]]
 
[[Category:FHIR Resource Proposal]]
[[Category:Pending FHIR Resource Proposal]]
+
[[Category:Approved FHIR Resource Proposal]]
  
  
Line 13: Line 12:
  
  
=PutProposedResourceNameHere=
+
=Group=
  
 
<!-- Resource names should meet the following characteristics:
 
<!-- Resource names should meet the following characteristics:
Line 30: Line 29:
  
 
<!-- 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]]
+
Will be one of [[Public_Health_and_Emergency_Response_work_group_(PHER)|Public Health & Emergency Response]] or [[Patient_Administration|Patient Administration Working Group]] but up to the completion of the first ballot it is temporarily owned by FHIR Core Team
  
 
==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) -->
+
<!-- Additional work groups that may have an interest in contributing to, or reviewing  the content of the resource (optional)  
 
* Work Group Name
 
* Work Group Name
 
* or link
 
* or link
* or "None"
+
* or "None" -->
 
+
All work groups may have cause to use this resource at some time, but no one group has a special requirement.
 +
 
==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 -->
 +
pending
  
 
==Scope of coverage==
 
==Scope of coverage==
Line 55: Line 56:
 
As a rule, resources should encompass all of these aspects.
 
As a rule, resources should encompass all of these aspects.
 
  -->
 
  -->
 +
A ''group'' represents a defined collection of entities that may be discussed or acted upon collectively but which are not expected to act collectively and are not formally or legally recognized as such.  Members of such a group will be identifiable "things" of some form, for example Patients, Practitioners, Devices, Medicines.
 +
 +
Groups may have a business identifier and as such constitute an entity in their own right outside FHIR (unlike lists which may be of a specific type, but are not identifiable as list instances other than by means of their FHIR URL).
 +
 +
Groups may be defined by criteria for inclusion or by enumeration (unlike lists which can only be enumerated).  As well, the specific members of the Group may not be known - or even relevant, while with List, they must always be known.
  
 
==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. -->
 +
Entity[determinerCode="KIND"]
 +
 +
classCode may be used to further specify the type of resource that the group refers to.  Specific members are instances used to define the "kind"
  
 
==Resource appropriateness==
 
==Resource appropriateness==
Line 74: Line 83:
 
* Have the characteristics of high cohesion & low coupling – need to explore whether coupling is good some places, not elsewhere – layers from Bo’s document  
 
* Have the characteristics of high cohesion & low coupling – need to explore whether coupling is good some places, not elsewhere – layers from Bo’s document  
 
  -->
 
  -->
 +
Dealing with collections of objects is a universal concept both in healthcare and in information modelling.  Most commonly used in public health, clinical trials, research, etc.
  
 
==Expected implementations==
 
==Expected 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. -->
 
<!--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. -->
 +
 +
Most real world implementations will have to use this concept at some point.  In part created to ensure that existing structures aren't misused
  
 
==Content sources==
 
==Content sources==
Line 84: Line 96:
  
 
Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? -->
 
Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? -->
 +
* PHER DMIM
 +
* RCRIM DMIM (eligibility criteria)
  
 
==Example Scenarios==
 
==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.) -->
 
<!-- 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.) -->
 +
 +
# Defining a set of patients participating in a group therapy
 +
# Defining 3 different treatment groups
 +
# Listing available devices for use
  
 
==Resource Relationships==
 
==Resource Relationships==
Line 99: Line 117:
 
Reference to resources is really only relevant at the "same or higher level" (Bo – fix this wording)
 
Reference to resources is really only relevant at the "same or higher level" (Bo – fix this wording)
 
  -->
 
  -->
 +
[[User:Hugh Glover|Hugh Glover]] 10:10, 18 June 2013 (UTC): This is a very generic - any offers for some additional specific uses ...
 +
# Any resource that has a subject may have reason to refer to a group rather than an individual - Document and DeviceObservation do this as can MedicationPrescription.
 +
# Group links to the resource instances that are members of the group
  
 
==Timelines==
 
==Timelines==
  
 
<!-- 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 -->
 +
Ready for ballot in September 2013
  
 
==gForge Users==
 
==gForge Users==
  
 
<!-- 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.) -->
 +
 +
n/a
 +
 +
==Issues==
 +
[[User:Hugh Glover|Hugh Glover]] 10:10, 18 June 2013 (UTC) Not sure about scope, definition implies member of group could be any resource, but the group resource definition only explicitly mentions Patient, Practitioner, Device and Medication.
 +
 +
[[User:Hugh Glover|Hugh Glover]] 10:10, 18 June 2013 (UTC): Any offers for a more specific implementation?

Latest revision as of 05:41, 22 May 2014



Group

Owning committee name

Will be one of Public Health & Emergency Response or Patient Administration Working Group but up to the completion of the first ballot it is temporarily owned by FHIR Core Team

Contributing or Reviewing Work Groups

All work groups may have cause to use this resource at some time, but no one group has a special requirement.

FHIR Resource Development Project Insight ID

pending

Scope of coverage

A group represents a defined collection of entities that may be discussed or acted upon collectively but which are not expected to act collectively and are not formally or legally recognized as such. Members of such a group will be identifiable "things" of some form, for example Patients, Practitioners, Devices, Medicines.

Groups may have a business identifier and as such constitute an entity in their own right outside FHIR (unlike lists which may be of a specific type, but are not identifiable as list instances other than by means of their FHIR URL).

Groups may be defined by criteria for inclusion or by enumeration (unlike lists which can only be enumerated). As well, the specific members of the Group may not be known - or even relevant, while with List, they must always be known.

RIM scope

Entity[determinerCode="KIND"]

classCode may be used to further specify the type of resource that the group refers to. Specific members are instances used to define the "kind"

Resource appropriateness

Dealing with collections of objects is a universal concept both in healthcare and in information modelling. Most commonly used in public health, clinical trials, research, etc.

Expected implementations

Most real world implementations will have to use this concept at some point. In part created to ensure that existing structures aren't misused

Content sources

  • PHER DMIM
  • RCRIM DMIM (eligibility criteria)

Example Scenarios

  1. Defining a set of patients participating in a group therapy
  2. Defining 3 different treatment groups
  3. Listing available devices for use

Resource Relationships

Hugh Glover 10:10, 18 June 2013 (UTC): This is a very generic - any offers for some additional specific uses ...

  1. Any resource that has a subject may have reason to refer to a group rather than an individual - Document and DeviceObservation do this as can MedicationPrescription.
  2. Group links to the resource instances that are members of the group

Timelines

Ready for ballot in September 2013

gForge Users

n/a

Issues

Hugh Glover 10:10, 18 June 2013 (UTC) Not sure about scope, definition implies member of group could be any resource, but the group resource definition only explicitly mentions Patient, Practitioner, Device and Medication.

Hugh Glover 10:10, 18 June 2013 (UTC): Any offers for a more specific implementation?