Salesforce Health Cloud Developer Guide

Health Cloud Developer Guide
Health Cloud Data Model
Advanced Therapy Management
Adverse Events
Assessment Generation
Benefits Verification
Care Program Management
Clinical Data Model
Predecessors to Code Sets and Code Set Bundles in Health Cloud
Coverage Requirement Discovery
Crisis Support Center Management
Documentation Templates and Rules
Disease Surveillance
Electronic Signatures
Engagement Interaction
FHIR Subscription
Financial Assistance Program
Health Assessments
Health Insurance
Home Health
Integrated Care Management
Intelligent Appointment Management
Practitioner Availability at Facilities
AppointmentReason
ApptReasonEngmtChannelType
AssetType
CarePractnFacilityAppt
ClinicalEncounter
ServiceAppointmentAsset
WorkTypeAssetType
WorkTypeCareSpecialty
WorkTypeCodeSetBundle
Intelligent Document Automation
Intelligent Sales
Medication Management
Patient Program Outcome Management
Participant Management
Patient Segmentation
Pharmacy Benefits Verification
Provider Network Management
Provider Relationship Management
Remote Monitoring and Device Registration
Social Determinants
Timeline
Unified Health Scoring
Utilization Management
ProductRequest
Health Cloud Associated Objects
Health Cloud Fields on Standard Objects
Health Cloud Platform Events
Working With Electronic Health Records
Emergency Response Management
Apex Reference
Health Cloud Business APIs
Health Cloud Tooling API Objects
Health Cloud Standard Invocable Actions
Metadata Types
Health Cloud FHIR APIs
MuleSoft Direct Integrations
API End-of-Life Policy
PDF

Practitioner Availability at Facilities

To book an appointment, we need to know the availability of a given practitioner at a given facility. To get this information, Health Cloud queries the specific source EHR system, using the IDs of the practitioner and the facility as stored in that source system.

Practitioner and Facility IDs

  • The source system ID comes from the Healthcare Practitioner Facility record for the practitioner+facility combination.
  • The source system facility ID comes from an Identifier record that looks up to the Contact record for the practitioner, with the same source system as the Healthcare Practitioner Facility record.
  • The source system facility ID comes from an Identifier record that looks up to the Account record for the facility, with the same source system as the Healthcare Practitioner Facility record.

Booking an appointment against a facility alone, such as an X-Ray, lab work, or dialysis, is not supported. A practitioner must be defined for the facility, even if it is a placeholder.

Practitioner+Facility Data Model

What's the difference between an ID and an Identifier?

  • An Identifier is a record type that represents real-world identifying information about a facility or practitioner, such as dates of validity, jurisdiction, and the issuing authority.
  • An ID is a machine-generated foreign key that identifies a record in a remote EHR system.

Note

Appointment Type and Service Type

The source system requires Appointment Type and Service Type codes that are derived from the “visit type” (Work Type record) selected by the call center agent. These codes are configured via Work Type Code Set Bundle records, one per Work Type, with lookups to Code Set Bundle and Code Sets for the Service Type and Appointment Type codes in each Source System the org integrates with.

Appointment Type and Service Type Data Model

Appointments booked by the call center agent result in a Service Appointment record being created along with a Healthcare Practitioner Facility Appointment junction between the Service Appointment and Healthcare Practitioner Facility. The Service Appointment status field is set to Booked upon record creation.

Appointment Data Model