This wiki has undergone a migration to Confluence found Here
Difference between revisions of "List FHIR Resource Proposal"
Jump to navigation
Jump to search
Hugh Glover (talk | contribs) |
|||
| Line 12: | Line 12: | ||
| − | = | + | =List= |
<!-- Resource names should meet the following characteristics: | <!-- Resource names should meet the following characteristics: | ||
| Line 29: | 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. --> | ||
| + | Owned by Patient Care, though temporarily being managed by the FHIR Core Team | ||
| + | |||
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 | 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== | ||
| Line 58: | Line 58: | ||
As a rule, resources should encompass all of these aspects. | As a rule, resources should encompass all of these aspects. | ||
--> | --> | ||
| − | A ''list'' represents a collection of resources that is defined by enumeration and may be ordered. The contents of a list may change over time and there may be a record kept of items that it did contain but have now been deleted. | + | A ''list'' represents a currated collection of resources that is defined by enumeration and may be ordered. The contents of a list may change over time and there may be a record kept of items that it did contain but have now been deleted. |
| − | A list is similar to a group but is not an exact specialisation of a group. | + | A list is similar to a group but is not an exact specialisation of a group. A List always has a specific context or semantic that identifies the purpose of the collected entities. The context of groups is determinable only by where they are referenced. |
Groups may have a business identifier and as such constitute an entity in their own right outside FHIR. In contrast 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 have a business identifier and as such constitute an entity in their own right outside FHIR. In contrast lists which may be of a specific type, but are not identifiable as list instances other than by means of their FHIR URL. | ||
| Line 67: | Line 67: | ||
Groups cannot be ordered, and have no concept of former members who have now been deleted. | Groups cannot be ordered, and have no concept of former members who have now been deleted. | ||
| − | |||
| − | |||
==RIM scope== | ==RIM scope== | ||
| Line 89: | Line 87: | ||
* 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. | + | Dealing with collections of objects is a universal concept both in healthcare and in information modelling. Needed for allergy, medication, problem and other lists |
==Expected implementations== | ==Expected implementations== | ||
| Line 95: | Line 93: | ||
<!--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. --> | ||
| − | + | Needed for CCDA | |
| − | |||
==Content sources== | ==Content sources== | ||
| Line 103: | Line 100: | ||
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? --> | ||
| − | + | *CCDA | |
| + | * Patient Care DMIM | ||
| + | * OpenEHR? | ||
==Example Scenarios== | ==Example Scenarios== | ||
| Line 112: | Line 111: | ||
# Providing a snapshot of the items dispensed to a patient in the last 3 months | # Providing a snapshot of the items dispensed to a patient in the last 3 months | ||
# Listing a patient's allergies and intolerances | # Listing a patient's allergies and intolerances | ||
| − | # Listing changes in a patient's | + | # Listing changes in a patient's problems since they were last assessed |
==Resource Relationships== | ==Resource Relationships== | ||
| Line 124: | Line 123: | ||
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) | ||
--> | --> | ||
| − | |||
#any resource that is an event or entity of some form may be summarised and managed by means of a list. | #any resource that is an event or entity of some form may be summarised and managed by means of a list. | ||
| Line 137: | Line 135: | ||
n/a | n/a | ||
| + | |||
| + | ==Issue== | ||
| + | [[User:Hugh Glover|Hugh Glover]] 10:55, 18 June 2013 (UTC): Not sure the distinction between group and list is sufficient to justify them being separate resources. | ||
| + | * LM: I'm quite certain they're distinct resources, but we definitely need to be clearer about what the boundaries are. | ||
Revision as of 15:39, 3 July 2013
This page documents a Pending FHIR Resource Proposal
Contents
- 1 List
- 1.1 Owning committee name
- 1.2 Contributing or Reviewing Work Groups
- 1.3 FHIR Resource Development Project Insight ID
- 1.4 Scope of coverage
- 1.5 RIM scope
- 1.6 Resource appropriateness
- 1.7 Expected implementations
- 1.8 Content sources
- 1.9 Example Scenarios
- 1.10 Resource Relationships
- 1.11 Timelines
- 1.12 gForge Users
- 1.13 Issue
List
Owning committee name
Owned by Patient Care, though temporarily being managed by the FHIR Core Team
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 list represents a currated collection of resources that is defined by enumeration and may be ordered. The contents of a list may change over time and there may be a record kept of items that it did contain but have now been deleted.
A list is similar to a group but is not an exact specialisation of a group. A List always has a specific context or semantic that identifies the purpose of the collected entities. The context of groups is determinable only by where they are referenced.
Groups may have a business identifier and as such constitute an entity in their own right outside FHIR. In contrast 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 whereas lists which can only be enumerated.
Groups cannot be ordered, and have no concept of former members who have now been deleted.
RIM scope
Act[normalAct() and subsumes(ActClass#_ActClassRecordOrganizer, classCode) and moodCode=EVN]
Resource appropriateness
Dealing with collections of objects is a universal concept both in healthcare and in information modelling. Needed for allergy, medication, problem and other lists
Expected implementations
Needed for CCDA
Content sources
- CCDA
- Patient Care DMIM
- OpenEHR?
Example Scenarios
- Keeping a running list of patients in a ward
- Providing a snapshot of the items dispensed to a patient in the last 3 months
- Listing a patient's allergies and intolerances
- Listing changes in a patient's problems since they were last assessed
Resource Relationships
- any resource that is an event or entity of some form may be summarised and managed by means of a list.
Timelines
Ready for ballot in September 2013
gForge Users
n/a
Issue
Hugh Glover 10:55, 18 June 2013 (UTC): Not sure the distinction between group and list is sufficient to justify them being separate resources.
- LM: I'm quite certain they're distinct resources, but we definitely need to be clearer about what the boundaries are.
