This wiki has undergone a migration to Confluence found Here

Difference between revisions of "Person FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
Line 80: Line 80:
  
 
<!--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. -->
 +
 +
* Cross-Domain Patient Directory
 +
* Cross Domain Provider Directory
 +
* Client Portal
  
 
==Content sources==
 
==Content sources==

Revision as of 12:07, 18 February 2015



Person

Owning committee name

Patient Administration

Contributing or Reviewing Work Groups

  • or "None"

FHIR Resource Development Project Insight ID

pending

Scope of coverage

A natural person has identity outside of a healthcare setting. The Person resource is used to capture this information and to relate the person as an individual to other resources that do have a health-related context.

RIM scope

This Person Resource is not covered by the RIM directly.

Resource appropriateness

Expected implementations

  • Cross-Domain Patient Directory
  • Cross Domain Provider Directory
  • Client Portal

Content sources

None.

Example Scenarios

Patient/RelatedPerson linkages:

  • In many systems an individual entered as a RelatedPerson entry is also linked to a Patient entry when entered.

This reduces the amount of data entry required for users, as it is known that this is the same individual.

Cross-Domain Patient Directory:

  • In a data sharing network, finding the location of patient records across different systems is a necessary pre-requisite for accessing external patient data. Using the link element, systems associate patient resources from different organizations. The assuranceLevel associated with the link provides a way for a system to qualify its confidence in the asserted link. For example, a relationship from the person to a patient using a probabilistic matching algorithm may be represented using a link with an assurance level of level1, while a relationship established using a government-issued photo ID may be created with an assurance level of level3.

Cross Domain Provider Directory:

  • Similarly, providers working in multiple healthcare service settings may be linked across different organizations using the link element. The various practitioner resources can be related using a common person resource with a link for each of the practitioner resources located in other organizations.

Client Portal:

  • In a client portal used by the consumers the Person record could be used to form a kind of "Account" within the system and links to all the other related systems where their data is stored/referenced.

Resource Relationships

The Person resource provides direct links to Patient, Practitioner, RelatedPerson, and Person (itself)

There are no links created that point towards the Person resource.

Timelines

This resource has been worked on by the workgroup and reviewed in the for comment ballot just reconciled.

gForge Users

brianpos, ewoutkramer, grahameg