---
# System prepended metadata

title: FHIR PHR
tags: [fhir-project]

---

---
title: FHIR PHR
tags: fhir-project
---

<font color="red">FHIR</font> Personal Health Record (PHR)
===
###### tags: `fhir-project` `phr`

## Table of Contents
[TOC]

## Introduction 
In the PHR scenario, an Electronic Medical Record system (EMR, though many other names and acronyms are also used) provides a RESTful API that allows patients to access their own medical record via a common web portal or mobile application, usually provided by a third party. In this scenario, the PHR provider:

Provides the patient with a login that identifies them (or links the patient record to an external identity provided by OpenID, Facebook, Google, etc.)
Authenticates the client using an appropriate OAuth server for the login (possibly their own) and restricts the client to viewing records associated with the specific patient (or patients, where appropriate access has been arranged)
The EMR exposes a FHIR server that supports the search and read operations on the following resources:

the Patient resource in order to provide demographics to the client. When a client searches patients with no search criteria, they get a list of all patients they have access to
search and read on the Document Reference resource to provide access to general patient documents in the form of PDFs etc. (PDFs are preferred)
search and read on a set of clinical resources
Here is the Capabilities Statement for this scenario: XML or JSON.

![](https://i.imgur.com/mkruHw2.png)
IBM -> Organization (healthcare provider)
