This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Patient FHIR Resource Proposal"
Jump to navigation
Jump to search
m (Created page with "{{subst::Template:FHIR Resource Proposal}}") |
|||
| (8 intermediate revisions by 3 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 | + | 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: | + | [[Category:Approved FHIR Resource Proposal]] |
| Line 13: | Line 12: | ||
| − | = | + | =Patient= |
<!-- 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. --> | ||
| − | [[ | + | [[Patient_Administration]] |
==Contributing or Reviewing Work Groups== | ==Contributing or Reviewing Work Groups== | ||
| + | RCRIM may be involved in reviewing from a "study subject" perspective | ||
<!-- 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) --> | ||
| − | + | No other workgroups are involved | |
| − | |||
| − | |||
==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 | |
==Scope of coverage== | ==Scope of coverage== | ||
| Line 55: | Line 53: | ||
As a rule, resources should encompass all of these aspects. | As a rule, resources should encompass all of these aspects. | ||
--> | --> | ||
| + | Demographics and other administrative information about a person or animal receiving care or other health-related services. This Resource covers data about persons and animals involved in a wide range of health-related activities, including: | ||
| + | *Curative activities | ||
| + | *Psychiatric care | ||
| + | *Social services | ||
| + | *Pregnancy care | ||
| + | *Nursing and assisted living | ||
| + | *Dietary services | ||
| + | *Tracking of personal health and exercise data | ||
| + | *Financial claims and administrative activities | ||
| + | The data in the Resource covers the "who" information about the patient: Its attributes are focused on the demographic information necessary to support the administrative, financial and logistic procedures and does not contain medical or care-related information. Data may be time-dependent but should not be opinion-dependent. | ||
==RIM scope== | ==RIM scope== | ||
| − | + | Patient | |
<!-- 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. --> | ||
==Resource appropriateness== | ==Resource appropriateness== | ||
| + | Patients are ubiquitous in healthcare and almost all systems track them. Patients are assigned patient id's and their demographics data is tracked and kept up-to-date. Patient data has been part of HL7 since version 2. | ||
<!-- Does the resource meet the following characteristics? | <!-- Does the resource meet the following characteristics? | ||
| Line 76: | Line 85: | ||
==Expected implementations== | ==Expected implementations== | ||
| − | + | Almost all systems need to have some patient data. Also present in CCDA. | |
<!--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== | ||
| + | CIMI, Norwegian Person Registry v3 implementation manuals, v2 PID & PD1, v3 Patient CMETs, OpenEHR | ||
<!-- 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 86: | Line 96: | ||
==Example Scenarios== | ==Example Scenarios== | ||
| + | * A patient in the hospital patient registration | ||
| + | * An animal registered in a veterinary clinic | ||
<!-- 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.) --> | ||
==Resource Relationships== | ==Resource Relationships== | ||
| + | This resource references Organization and Picture. It is expected almost all Resources will refer to Patient. | ||
<!-- 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 101: | Line 114: | ||
==Timelines== | ==Timelines== | ||
| + | Expected to be ready for sept 2013 DSTU | ||
<!-- 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, Alexander Henket | ||
| + | <!-- Identify the userids who will require commit access to gForge to maintain the resource. (Ensure all users have registered for gForge.) --> | ||
| − | + | ==Issues== | |
| + | * Some tweaks made to scope & mapping sources | ||
| + | * Need example scenarios added | ||
Latest revision as of 05:47, 22 May 2014
This page documents an Approved FHIR Resource Proposal
Contents
- 1 Patient
- 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 Issues
Patient
Owning committee name
Contributing or Reviewing Work Groups
RCRIM may be involved in reviewing from a "study subject" perspective
No other workgroups are involved
FHIR Resource Development Project Insight ID
925
Scope of coverage
Demographics and other administrative information about a person or animal receiving care or other health-related services. This Resource covers data about persons and animals involved in a wide range of health-related activities, including:
- Curative activities
- Psychiatric care
- Social services
- Pregnancy care
- Nursing and assisted living
- Dietary services
- Tracking of personal health and exercise data
- Financial claims and administrative activities
The data in the Resource covers the "who" information about the patient: Its attributes are focused on the demographic information necessary to support the administrative, financial and logistic procedures and does not contain medical or care-related information. Data may be time-dependent but should not be opinion-dependent.
RIM scope
Patient
Resource appropriateness
Patients are ubiquitous in healthcare and almost all systems track them. Patients are assigned patient id's and their demographics data is tracked and kept up-to-date. Patient data has been part of HL7 since version 2.
Expected implementations
Almost all systems need to have some patient data. Also present in CCDA.
Content sources
CIMI, Norwegian Person Registry v3 implementation manuals, v2 PID & PD1, v3 Patient CMETs, OpenEHR
Example Scenarios
- A patient in the hospital patient registration
- An animal registered in a veterinary clinic
Resource Relationships
This resource references Organization and Picture. It is expected almost all Resources will refer to Patient.
Timelines
Expected to be ready for sept 2013 DSTU
gForge Users
ewoutkramer, Alexander Henket
Issues
- Some tweaks made to scope & mapping sources
- Need example scenarios added
