Skip to main content

 –

Key rules in business request API execution

Suggest edit Updated on September 18, 2020

Each pre-configured FHIR API in the Foundation has the following rules configured for it:

Rule nameRule typeUsage
D_FHIR<Resource> e.g. D_FHIRMemberData PageCalls the connector and identifies the request and response mapping rules.
<ResourceName> e.g., PatientConnect RESTCalls the REST Service using endpoint URL.
Map<Resource>RequestDataData TransformMaps the request data.
MapTo<Resource> e.g., MapToMembersData TransformWrapper rule which calls the main mapping data transform rule.
MapTo<Resource> e.g., MapToMemberDetailsData TransformMapping data transform which maps the results to the response.
Did you find this content helpful? YesNo

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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