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 |
Ewoutkramer (talk | contribs) |
||
| Line 52: | Line 52: | ||
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. | + | 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: |
| − | |||
| − | |||
| − | |||
| − | This Resource covers data about persons and animals involved in a wide range of health-related activities, including: | ||
| − | |||
*Curative activities | *Curative activities | ||
*Psychiatric care | *Psychiatric care | ||
| Line 65: | Line 60: | ||
*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. | |
| − | + | ||
==RIM scope== | ==RIM scope== | ||
| − | + | Person, NonPersonLivingSubject, 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== | ||
| − | |||
<!-- Does the resource meet the following characteristics? | <!-- Does the resource meet the following characteristics? | ||
| Line 87: | Line 81: | ||
==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 | ||
<!-- 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 101: | Line 96: | ||
==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 112: | Line 108: | ||
==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.) --> | <!-- Identify the userids who will require commit access to gForge to maintain the resource. (Ensure all users have registered for gForge.) --> | ||
Revision as of 08:37, 5 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
Patient
Owning committee name
Contributing or Reviewing Work Groups
- "None"
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
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.
RIM scope
Person, NonPersonLivingSubject, Patient
Resource appropriateness
Expected implementations
Almost all systems need to have some patient data. Also present in CCDA.
Content sources
CIMI, Norwegian Person Registry v3 implementation manuals
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
