Difference between revisions of "Patient FHIR Resource Proposal"
Ewoutkramer (talk | contribs) m |
|||
| Line 32: | Line 32: | ||
==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) --> | ||
| Line 60: | Line 61: | ||
*Dietary services | *Dietary services | ||
*Tracking of personal health and exercise data | *Tracking of personal health and exercise data | ||
| − | 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. | + | *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. --> | ||
| Line 87: | Line 89: | ||
==Content sources== | ==Content sources== | ||
| − | CIMI, Norwegian Person Registry v3 implementation manuals | + | 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 98: | Line 100: | ||
==Resource Relationships== | ==Resource Relationships== | ||
| − | This resource references Organization and Picture. It is expected almost all Resources will refer to | + | 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 117: | Line 119: | ||
ewoutkramer, Alexander Henket | ewoutkramer, Alexander Henket | ||
<!-- 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.) --> | ||
| + | |||
| + | ==Issues== | ||
| + | * Some tweaks made to scope & mapping sources | ||
Revision as of 17:56, 12 June 2013
This page documents a Pending 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
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
