Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Encounter: GET Encounter list

Updated on October 19, 2021

The FHIR Encounter resource is an interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient. The Search interaction enables the client to query for all the Encounters that have been filed for a patient given search parameters.

Pega Foundation for Healthcare

Read operation

Parameters

Key rules

Rule NameRule TypeUsage
Class: Int-PegaHC-Data-Encounter
EncounterConnect REST
D_FHIR4EncounterReadData PageTo call connector and map request and response
EncounterReadFHIR4Connect RESTCall REST Service using endpoint URL
MapToEncounter4ReadData TransformTo map result data to data page
MapToEncounter4DetailsData TransformMap results to PFHC Encounter object
Pre_MapToEncounter4Read_ExtData TransformTo be used for extension
Post_MapToEncounter4Read_ExtData TransformTo be used for extension
Pre_MapToEncounter4Details_ExtData TransformTo be used for extension
Post_MapToEncounter4Details_ExtData TransformTo be used for extension

Search operation

Key rules

Rule NameRule TypeUsage
Class:PegaHC-Data-Encounter
EncounterConnect REST
D_FHIR4EncounterData PageTo call connector and map request and response
EncounterFHIR4Connect RESTCall REST Service using endpoint URL
MapToEncounter4Data TransformTo map result data to data page
MapToEncounter4DetailsData TransformMap results to PFHC Encounter object
Pre_MapToEncounter4_ExtData TransformTo be used for extension
Post_MapToEncounter4_ExtData TransformTo be used for extension
Pre_MapToEncounter4Details_ExtData TransformTo be used for extension
Post_MapToEncounter4Details_ExtData TransformTo be used for extension

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us