Patient

A person receiving healthcare services, serving as the central entity in the healthcare domain. Patient extends Person with clinical and administrative attributes specific to healthcare delivery.

Overview

The Patient entity captures all information necessary to identify, contact, and provide care to an individual within a healthcare system. It inherits demographic and contact information from Person while adding healthcare-specific properties such as biological sex, blood type, and care team associations.

Key Concepts

Identity & Demographics

Patient inherits core identity from Person:

givenName, familyName, middleName - Legal name components
birthDate - Date of birth for age calculations
gender - Gender identity (via Gender)
telecoms - Contact points (phone, email) via ContactPoint
address - Physical addresses via PostalAddress
identifier - Official IDs (national ID, passport) via Identifier

Patient adds healthcare-specific identity:

biologicalSex - Administrative sex for clinical purposes via PatientBiologicalSex
pseudonym - Anonymized identifier for de-identified data
birthCity, birthCountry - Birth location details

Clinical Information

bloodType - ABO/Rh blood type via PatientBloodType for transfusion compatibility
multipleBirth - Twin/triplet indicator with birthOrder for birth sequence

Care Team

generalPractitioner - Primary care physician via Practitioner
managingFacility - Healthcare facility managing this record via Facility

Record Status

The status field tracks the administrative state of the patient record:

active - Current patient receiving care
inactive - Patient no longer receiving care at this facility
deceased - Patient has died (see deceasedDate)
merged - Record merged into another patient record
unknown - Status cannot be determined

Related Entities

Patient is the central entity referenced by many healthcare entities:

Entity	Relationship	Description
PatientAllergy	Patient has many	Allergies and intolerances
PatientContact	Patient has many	Emergency contacts and guardians
PatientCoverage	Patient has many	Insurance coverage information
PatientMedicalCondition	Patient has many	Chronic conditions and medical history
PatientDietaryRegime	Patient has many	Dietary restrictions and meal plans
PatientAdvanceDirective	Patient has many	Living wills and healthcare proxies
PatientAdministrativeDocument	Patient has many	Identity and insurance documents
Encounter	Patient has many	Clinical visits and admissions
Diagnosis	Patient has many	Medical diagnoses
Prescription	Patient has many	Medication orders
LaboratoryOrder	Patient has many	Lab test requests

FHIR Mapping

RocketSchema	FHIR R5 Patient
Patient	Patient
givenName	name.given
familyName	name.family
birthDate	birthDate
biologicalSex	gender (administrative)
gender	genderIdentity (extension)
status	active
deceasedDate	deceasedDateTime
multipleBirth	multipleBirthBoolean
birthOrder	multipleBirthInteger
generalPractitioner	generalPractitioner
managingFacility	managingOrganization
telecoms	telecom
address	address

Enums

status

Value	Description
`active`	Patient record is active and receiving care
`inactive`	Patient no longer receiving care at this facility
`deceased`	Patient has died
`merged`	Record merged into another patient record
`unknown`	Status cannot be determined

Extends: Person

52 properties

Schema

Properties

Includes inherited properties from Person

Property	Type	Mode	Description	Required	Source
prefix	string	stored	Title or honorific (Mr., Mrs., Ms., Dr., Prof., etc.) Example: `"Dr."`	Optional	Person
givenName	string	stored	First name or given name Example: `"John"`	Required	Person
middleName	string	stored	Middle name(s) Example: `"Michael"`	Optional	Person
familyName	string	stored	Last name or family name Example: `"Doe"`	Required	Person
suffix	string	stored	Name suffix (Jr., Sr., III, PhD, MD, etc.) Example: `"Jr."`	Optional	Person
preferredName	string	stored	Name the person prefers to be called Example: `"Johnny"`	Optional	Person
status	string	enum	Current status Values: `active, inactive, deceased` Example: `"active"`	Optional	Person
gender	Gender	stored	Gender identity (reference to Gender entity)	Optional	Person
maritalStatus	MaritalStatus	stored	Marital status (reference to MaritalStatus entity)	Optional	Person
birthDate	Date	stored	Date of birth Example: `"1990-01-15"`	Optional	Person
nationality	Country[]	stored	Nationality or citizenship - supports multiple nationalities (reference to Country entity)	Optional	Person
languages	LanguageProficiency[]	stored	Languages spoken by the person with proficiency levels	Optional	Person
telecoms	ContactPoint[]	stored	Contact points - phone numbers, emails, etc.	Optional	Person
onlinePresence	OnlinePresence[]	stored	Online profiles and social media	Optional	Person
address	PostalAddress[]	stored	Physical addresses	Optional	Person
photoUrl	string	stored	URL to person's photograph or avatar Example: `"https://example.com/photos/person.jpg"`	Optional	Person
identifier	Identifier[]	stored	Official identifiers - national ID, passport, driver's license, etc.	Optional	Person
metadata	object	stored	Additional metadata for extensibility	Optional	Person
biologicalSex	PatientBiologicalSex	stored	Administrative sex for clinical purposes (distinct from gender identity in Person)	Optional	Patient
pseudonym	string	stored	Anonymized identifier used when patient data is de-identified	Optional	Patient
birthCity	string	stored	City where the patient was born	Optional	Patient
birthCountry	Country	stored	Country where the patient was born	Optional	Patient
countryOfOrigin	Country	stored	Patient's country of origin or ancestral heritage	Optional	Patient
maritalStatus	MaritalStatus	stored	Current marital status of the patient	Optional	Patient
numberOfChildren	number	stored	Total number of children the patient has Example: `2`	Optional	Patient
dependentChildren	number	stored	Number of dependent children currently under patient's care Example: `1`	Optional	Patient
status	string	stored	Current administrative status of the patient record Values: `active, inactive, deceased, merged, unknown` Example: `"active"`	Required	Patient
deceasedDate	DateTime	stored	Date and time of death if the patient is deceased	Optional	Patient
multipleBirth	boolean	stored	Whether the patient is part of a multiple birth (twins, triplets, etc.)	Optional	Patient
birthOrder	number	stored	Birth order if part of multiple birth (1 for first born, 2 for second, etc.) Example: `1`	Optional	Patient
generalPractitioner	Practitioner	stored	Reference to the patient's nominated primary care physician	Optional	Patient
managingFacility	Facility	stored	Healthcare facility that is the custodian of the patient record	Optional	Patient
bloodType	PatientBloodType	stored	Patient's blood type for transfusion compatibility	Optional	Patient
notes	string	stored	Administrative notes and special considerations for patient care	Optional	Patient

Examples

Example 1

{
  "@type": "Patient",
  "givenName": "John",
  "familyName": "Smith",
  "birthDate": "1975-05-15",
  "gender": {
    "@type": "Gender",
    "code": "M",
    "label": "Male"
  },
  "biologicalSex": {
    "@type": "PatientBiologicalSex",
    "code": "male",
    "label": "Male"
  },
  "telecoms": [
    {
      "@type": "ContactPoint",
      "system": "phone",
      "value": "+1-555-0199",
      "use": "mobile"
    },
    {
      "@type": "ContactPoint",
      "system": "email",
      "value": "john.smith@example.com",
      "use": "home"
    }
  ],
  "address": [
    {
      "@type": "PostalAddress",
      "streetAddress": "789 Maple Ave",
      "addressLocality": "Boston",
      "addressRegion": "MA",
      "postalCode": "02115",
      "addressCountry": "US"
    }
  ],
  "status": "active",
  "multipleBirth": false,
  "generalPractitioner": {
    "@type": "Practitioner",
    "licenseNumber": "MD-MA-987654"
  },
  "managingFacility": {
    "@type": "Facility",
    "name": "City General Hospital"
  },
  "bloodType": {
    "@type": "PatientBloodType",
    "code": "O+",
    "aboGroup": "O",
    "rhFactor": "positive",
    "label": "O Positive"
  }
}

Example 2

{
  "@type": "Patient",
  "givenName": "Sarah",
  "familyName": "Johnson",
  "birthDate": "1989-11-22",
  "gender": {
    "@type": "Gender",
    "code": "F",
    "label": "Female"
  },
  "biologicalSex": {
    "@type": "PatientBiologicalSex",
    "code": "female",
    "label": "Female"
  },
  "telecoms": [
    {
      "@type": "ContactPoint",
      "system": "phone",
      "value": "+1-555-0277",
      "use": "mobile"
    }
  ],
  "status": "active",
  "multipleBirth": true,
  "birthOrder": 1,
  "bloodType": {
    "@type": "PatientBloodType",
    "code": "A+",
    "aboGroup": "A",
    "rhFactor": "positive",
    "label": "A Positive"
  }
}

Example 3

{
  "@type": "Patient",
  "givenName": "Robert",
  "familyName": "Williams",
  "birthDate": "1942-03-10",
  "gender": {
    "@type": "Gender",
    "code": "M",
    "label": "Male"
  },
  "biologicalSex": {
    "@type": "PatientBiologicalSex",
    "code": "male",
    "label": "Male"
  },
  "status": "deceased",
  "deceasedDate": "2024-06-15T14:30:00Z",
  "multipleBirth": false,
  "bloodType": {
    "@type": "PatientBloodType",
    "code": "B+",
    "aboGroup": "B",
    "rhFactor": "positive",
    "label": "B Positive"
  }
}