RelatedPerson FHIR Resource Proposal
Contents
- 1 RelatedPerson
- 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
RelatedPerson
Owning committee name
Contributing or Reviewing Work Groups
None
FHIR Resource Development Project Insight ID
925
Scope of coverage
Covers persons involved in healthcare, but that are not the target of healthcare, nor have a formal responsibility in the care process. Typically these are friends, relatives or others with a personal or non-healthcare-specific professional relationship to the patient (e.g. attorney, guardian, etc.). For animal patients, relationships might include owner, trainer, etc.
RIM scope
Role[classCode=REL]
Resource appropriateness
These persons are of interest because they may have responsibility for healthcare decisions, require notification of healthcare events or be responsible for the capture of reporting of healthcare information, however the information to be captured and tracked about these persons differs from that typically recorded for Patients or Practitioners. Commonly captured using "next of kin" and similar structures
Expected implementations
A subset of health information systems that keep track of identified related persons. Required by several resources used within CCDA
Content sources
ROL, NK1 in v2, RelatedPerson in v3, possibly also affiliate specifications, OpenEHR
Example Scenarios
- A patient's wife or husband
- A contact for a patient or organization
- A neighbour bringing a patient to the hospital
- Owner of a horse
Resource Relationships
None
Timelines
Considered for the sept 2013 DSTU ballot, but might be delayed until after that.
gForge Users
ewoutkramer
Issues
- Adjusted scope and rationale a bit, added one example