Practitioner

A healthcare provider authorized to deliver medical services. Extends Person with medical specialties, practice status, and patient acceptance indicators.

Overview

Practitioner represents any individual who provides healthcare services - physicians, nurses, pharmacists, therapists, and other clinical professionals. The entity inherits demographic and contact information from Person while adding healthcare-specific attributes: medical specialties, practice status, and whether the practitioner is accepting new patients. Practitioners are linked to facilities through PractitionerFacilityAffiliation and credentialed through PractitionerLicense and PractitionerQualification.

Key Concepts

Person Inheritance

Practitioner inherits from Person:

  • givenName, familyName, middleName - Legal name
  • birthDate - Date of birth
  • gender - Gender identity via Gender
  • telecoms - Contact points (phone, email) via ContactPoint
  • address - Addresses via PostalAddress
  • identifier - Official IDs (NPI, RPPS) via Identifier

Medical Specialties

The specialties array references HealthReferencePractitionerSpecialty:

  • A practitioner may have multiple specialties
  • Primary specialty is typically listed first
  • Subspecialties can be included
  • Used for referral routing and provider search

Common Specialties

  • General Practice, Internal Medicine, Family Medicine
  • Cardiology, Neurology, Oncology
  • Orthopedics, General Surgery
  • Pediatrics, OB/GYN

Practice Status

The status field tracks the practitioner's current ability to practice:

StatusMeaningCan Practice?
activeCurrently practicingYes
inactiveNot currently practicingNo
suspendedTemporarily barredNo
retiredPermanently stoppedNo

Patient Acceptance

The acceptingNewPatients boolean indicates:

  • true - Currently taking new patients
  • false - Panel is closed or limited availability

Use Cases

Provider Directory

For patient-facing search:

  1. Filter practitioners by specialty
  2. Show only active status providers
  3. Filter by acceptingNewPatients: true
  4. Display contact information from telecoms
  5. Link to affiliated facilities

Referral Management

When routing referrals:

  1. Identify required specialty for patient need
  2. Find practitioners with matching specialty
  3. Check status is active
  4. Verify accepting new patients
  5. Route referral to appropriate provider

Care Team Assignment

When assigning care teams:

  1. Select practitioners by specialty and facility
  2. Assign to patient encounters
  3. Document role in care team
  4. Enable care team communication

Credentialing Verification

When verifying providers:

  1. Check practitioner status is active
  2. Query associated licenses for validity
  3. Verify qualifications and board certifications
  4. Confirm facility privileges

Scheduling

For appointment booking:

  1. Display practitioners with relevant specialty
  2. Filter by accepting new patients
  3. Check availability at affiliated facilities
  4. Book appointment with selected provider

Related Entities

EntityRelationshipDescription
PersonExtendsBase person demographic information
HealthReferencePractitionerSpecialtyReferences manyMedical specialties
PractitionerLicenseHas manyProfessional licenses by jurisdiction
PractitionerQualificationHas manyDegrees, certifications, fellowships
PractitionerFacilityAffiliationHas manyFacility and department assignments
PatientReferenced byPatients with this practitioner as GP
EncounterReferenced byClinical encounters involving this practitioner

Enums

status

ValueDescription
activePractitioner is currently practicing and authorized to provide care
inactivePractitioner is not currently practicing (leave, sabbatical, etc.)
suspendedPractitioner's practice privileges are temporarily suspended
retiredPractitioner has permanently retired from clinical practice
Extends: Person
39 properties
Schema

Properties

Includes inherited properties from Person

PropertyTypeModeDescriptionRequiredSource
prefixstring
stored

Title or honorific (Mr., Mrs., Ms., Dr., Prof., etc.)

Example: "Dr."

Optional
Person
givenNamestring
stored

First name or given name

Example: "John"

Required
Person
middleNamestring
stored

Middle name(s)

Example: "Michael"

Optional
Person
familyNamestring
stored

Last name or family name

Example: "Doe"

Required
Person
suffixstring
stored

Name suffix (Jr., Sr., III, PhD, MD, etc.)

Example: "Jr."

Optional
Person
preferredNamestring
stored

Name the person prefers to be called

Example: "Johnny"

Optional
Person
statusstring
enum

Current status

Values: active, inactive, deceased

Example: "active"

Optional
Person
genderGender
stored

Gender identity (reference to Gender entity)

Optional
Person
maritalStatusMaritalStatus
stored

Marital status (reference to MaritalStatus entity)

Optional
Person
birthDateDate
stored

Date of birth

Example: "1990-01-15"

Optional
Person
nationalityCountry[]
stored

Nationality or citizenship - supports multiple nationalities (reference to Country entity)

Optional
Person
languagesLanguageProficiency[]
stored

Languages spoken by the person with proficiency levels

Optional
Person
telecomsContactPoint[]
stored

Contact points - phone numbers, emails, etc.

Optional
Person
onlinePresenceOnlinePresence[]
stored

Online profiles and social media

Optional
Person
addressPostalAddress[]
stored

Physical addresses

Optional
Person
photoUrlstring
stored

URL to person's photograph or avatar

Example: "https://example.com/photos/person.jpg"

Optional
Person
identifierIdentifier[]
stored

Official identifiers - national ID, passport, driver's license, etc.

Optional
Person
metadataobject
stored

Additional metadata for extensibility

Optional
Person
specialtiesHealthReferencePractitionerSpecialty[]
stored

Medical specialties and areas of practice

Optional
Practitioner
statusstring
stored

Current practice status

Values: active, inactive, suspended, retired

Example: "active"

Required
Practitioner
acceptingNewPatientsboolean
stored

Whether currently accepting new patients

Example: true

Optional
Practitioner

Examples

Example 1

{
  "@type": "Practitioner",
  "givenName": "Michael",
  "familyName": "Chen",
  "birthDate": "1975-03-15",
  "gender": {
    "@type": "Gender",
    "code": "M",
    "label": "Male"
  },
  "telecoms": [
    {
      "@type": "ContactPoint",
      "system": "phone",
      "value": "+1-555-0100",
      "use": "work"
    },
    {
      "@type": "ContactPoint",
      "system": "email",
      "value": "michael.chen@hospital.com",
      "use": "work"
    }
  ],
  "specialties": [
    {
      "@type": "HealthReferencePractitionerSpecialty",
      "code": "CARDIO",
      "label": "Cardiology",
      "category": "medical"
    }
  ],
  "status": "active",
  "acceptingNewPatients": true
}

Example 2

{
  "@type": "Practitioner",
  "givenName": "Emily",
  "familyName": "Davis",
  "birthDate": "1982-08-22",
  "gender": {
    "@type": "Gender",
    "code": "F",
    "label": "Female"
  },
  "telecoms": [
    {
      "@type": "ContactPoint",
      "system": "phone",
      "value": "+1-555-0200",
      "use": "work"
    }
  ],
  "specialties": [
    {
      "@type": "HealthReferencePractitionerSpecialty",
      "code": "PEDS",
      "label": "Pediatrics",
      "category": "primary-care"
    }
  ],
  "status": "active",
  "acceptingNewPatients": false
}

Example 3

{
  "@type": "Practitioner",
  "givenName": "Sarah",
  "familyName": "Johnson",
  "birthDate": "1990-04-12",
  "gender": {
    "@type": "Gender",
    "code": "F",
    "label": "Female"
  },
  "telecoms": [
    {
      "@type": "ContactPoint",
      "system": "email",
      "value": "sarah.johnson@hospital.com",
      "use": "work"
    }
  ],
  "status": "active",
  "acceptingNewPatients": true
}