PegaHC FHIR Module - Healthcare API infrastructure
The Healthcare API infrastructure contains pre-configured connectors with specified
endpoint URL and populates the returned result in data pages that map the result to
Healthcare data model. The following diagram illustrates the flow of execution: The following list shows all the data pages and Connect REST APIs configured for read
and search operations for each of the FHIR Resources supported in this release and described
in the Overview section. Read ConditionReadFHIR4 Search ConditionFHIR4 Read PegaHC-Data-Policy CoverageReadFHIR4 Read Search DiagnosticReportFHIR4 Read EncounterReadFHIR4 D_FHIR4Encounter Search EncounterFHIR4 D_FHIR4EOBRead Read PegaHC-Data-Claim D_FHIR4EOB Search PegaHC-Data-Claim Read Search EpisodeOfCareFHIR4 Read D_FHIR4FamilyHistory Search Read D_FHIR4ImagingStudy Search ImagingStudyFHIR4 Read D_FHIR4Immunization Search ImmunizationFHIR4 Read MedicationReadFHIR4 D_FHIR4Medication Search MedicationFHIR4 Read Search Read Search Read ObservationReadFHIR4 D_FHIR4Observation Search ObservationFHIR4 D_FHIR4PatientRead Read PatientReadFHIR4 D_FHIR4Patient Search PatientFHIR4 Read PractitionerReadFHIR4 D_FHIR4Practitioner Search PractitionerFHIR4 Read Search PractitionerRoleFHIR4 Read ProcedureReadFHIR4 Search ProcedureFHIR4 D_FHIR4SlotRead Read SlotReadFHIR4 Likewise, we have below data pages with connectors configured to invoke EPIC FHIR
sandbox. Read PegaHC-Data-Allergies AllergiesReadFHIR4EPIC Search PegaHC-Data-Allergies AllergiesFHIR4EPIC Read PegaHC-Data-Observation ObservationReadFHIR4EPIC Search PegaHC-Data-Observation ObservationFHIR4EPIC Read PatientReadFHIR4EPIC Search PatientFHIR4EPIC Epic FHIR sandbox supports using the OAuth 2.0 framework to authenticate and authorize
applications. Hence, we need to configure authentication profile with OAuth2.0 to be
able to integrate with EPIC FHIR sandbox. For more details, refer to OAuth 2.0 tutorial
on https://fhir.epic.com/Documentation?docId=oauth2 Above OOTB data pages are configured with a sample Authentication profile called
‘EPICAuthentication’ as shown below. You need to update the configuration by following the oAuth 2.0 tutorial to be able to
run these data pages to invoke the service endpoints exposed by Open EPIC. Refer to Pega
online Help for additional information on configuring Authentication, Security Settings,
and Error Handling. The sample rules shown in the next few sections are shown using the “Member
(Patient)” resource as an example. Each published resource API has similar rules associated
with it. As shown below, the Source for the datapage is configured as a Connector which invokes
the external system REST service using the endpoint URL. The Endpoint URLs for all
configured services in Healthcare API are fetched through a dynamic settings data page
called D_FHIRSettings. The Connect REST rule supports the interaction between Pega and other systems over
the Hypertext Transfer Protocol (HTTP). It identifies the resource path endpoint URL of the
source system to which this rule connects, and the parameters used to pass in the request.
Refer to Pega online Help for additional information on configuring Authentication, Security
Settings, and Error Handling. Connect REST rule reads the EndpointUrl from application setting rule which in turn
invokes D_FHIRSettings Data page. The End Point URL resource path configured on a Connect REST rule cannot be modified
once the rule is finalized and locked. To be able to maintain different endpoint system URLs
and reference them dynamically, the Healthcare API configuration provide a pre-configured
node level dynamic settings data page called D_FHIRSettings. As shown above, this page is
referenced as a parameter to retrieve the EndPointURL for the given resource. The data source configured to fetch the end point URL is a Data Transform rule called
LoadFHIR4Settings. The rule is configured with URLs for a test reference system used
internally for testing the Healthcare APIs. The rule is marked for Extension and is
expected to be updated in your application with URLs for your own source systems for the
different resources. The MapToPatients4 data transform initiates the mapping of the response received from
the source system based on the number of result pages received. The rule initiates mapping
for each Member Resource in the response.
Accessing HC FHIR APIs
List of Published FHIR APIs as part of PegaHC FHIR Module
Resource DataPage Operation Data Type(Class) ConnectREST Allergy Intolerance D_FHIR4AllergyRead Read PegaHC-Data-Allergies AllergiesReadFHIR4 D_FHIR4Allergy Search PegaHC-Data-Allergies AllergiesFHIR4 Care Plan D_FHIR4CarePlanRead Read PegaHC-Data-CarePlan CarePlanReadFHIR4 D_FHIR4CarePlan Search PegaHC-Data-CarePlan CarePlanFHIR4 Condition (Problem) D_FHIR4ClinicalConditi onRead PegaHC-Data- ClinicalCondition D_FHIR4ClinicalConditi on PegaHC-Data- ClinicalCondition Coverage D_FHIR4CoverageRea d D_FHIR4Coverage Search PegaHC-Data-Policy CoverageFHIR4 Device D_FHIR4DeviceRead Read PegaHC-Data-Device DeviceReadFHIR4 D_FHIR4Device Search PegaHC-Data-Device DeviceFHIR4 Diagnostic Report D_FHIR4DiagnosticRep ortRead PegaHC-Data- DiagnosticReport DiagnosticReportReadF HIR4 D_FHIR4DiagnosticRep ort PegaHC-Data- DiagnosticReport Encounter D_FHIR4EncounterRea d PegaHC-Data- Encounter PegaHC-Data- Encounter Explanation of Benefits ExplanationOfBenefitRe adFHIR4 ExplanationOfBenefitFH IR4 Episode of Care D_FHIR4EpisodeOfCar eRead PegaHC-Data- EpisodeOfCare EpisodeOfCareReadFHI R4 D_FHIR4EpisodeOfCar e PegaHC-Data- EpisodeOfCare Family Member History D_FHIR4FamilyHistory Read PegaHC-Data- MedicalHistory FamilyMemberHistoryR eadFHIR4 PegaHC-Data- MedicalHistory FamilyMemberHistoryF HIR4 Goal D_FHIR4GoalRead Read PegaHC-Data-Goal GoalReadFHIR4 D_FHIR4Goal Search PegaHC-Data-Goal GoalFHIR4 Imaging Study D_FHIR4ImagingStudy Read PegaHC-Data- ImagingStudy ImagingStudyReadFHIR 4 PegaHC-Data- ImagingStudy Immunization D_FHIR4Immunization Read PegaHC-Data- Immunization ImmunizationReadFHIR 4 PegaHC-Data- Immunization Medication D_FHIR4MedicationRe ad PegaHC-Data- PatientMedications PegaHC-Data- PatientMedications Medication Dispense D_FHIR4MedicationDi spenseRead PegaHC-Data- PatientMedications MedicationDispenseRe adFHIR4 D_FHIR4MedicationDi spense PegaHC-Data- PatientMedications MedicationDispenseFHI R4 Medication Statement D_FHIR4MedicationSt atementRead PegaHC-Data- PatientMedications MedicationStatementR eadFHIR4 D_FHIR4MedicationSt atement PegaHC-Data- PatientMedications MedicationStatementF HIR4 Observation D_FHIR4ObservationR ead PegaHC-Data- Observation PegaHC-Data- Observation Patient PegaHC-Data-Party- Member PegaHC-Data-Party- Member Practitioner D_FHIR4PractitionerR ead PegaHC-Data-Party- Provider-Practitioner PegaHC-Data-Party- Provider-Practitioner Practitioner Role D_FHIR4PractitionerR oleRead PegaHC-Data-Party- Provider PractitionerRoleReadFH IR4 D_FHIR4PractitionerR ole PegaHC-Data-Party- Provider Procedure D_Fhir4ClinicalProced ureRead PegaHC-Data- ClinicalProcedure D_FHIR4ClinicalProced ure PegaHC-Data- ClinicalProcedure Schedule D_FHIR4ScheduleRead Read PegaHC-Data-Goal ScheduleReadFHIR4 D_FHIR4Schedule Search PegaHC-Data-Goal ScheduleFHIR4 Slot PegaHC-Data- AppointmentSchedule D_FHIR4Slot Search PegaHC-Data-AppointmentSchedule SlotFHIR4 Resource DataPage Operation Data Type(Class) ConnectREST Allergy Intolerance D_FHIR4AllergyRe adEPIC D_FHIR4AllergyEP IC Observatio n D_FHIR4Observat ionReadEPIC D_FHIR4Observat ionEPIC Patient D_FHIR4PatientR eadEPIC PegaHC-Data-Party- Member D_FHIR4PatientE PIC PegaHC-Data-Party- Member 
Detailed view of a Resource API in PegaHC FHIR Module:
Key rules in FHIR API execution
Rule name Rule type Usage D_FHIR4Patient Data Page Calls the connector and identifies the request and response mapping
rules. PatientFHIR4 Connect REST Calls the REST Service using endpoint URL. MapToPatients4 Data Transform Wrapper rule which calls the main mapping data transform
rule. MapToPatient4Details Data Transform Mapping data transform which maps the results to the
response. 
Connect REST rule
Dynamic Settings End Point URL Management Data Page
Map Response Data
Previous topic FHIR API component Next topic FHIR APIs: key rules