Skip to main content


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

Configuring a new API for a new FHIR Resource

Updated on October 19, 2021

The connector and data model are generated by using the REST Connector wizard.

Pega Foundation for Healthcare
  1. Log into your application using the administrator login.
  2. On the Dev Studio menu, navigate to Integration > Connectors > Create REST Integration.
  3. Configure the System details. Provide the FHIR end-point URL of desired resource as shown below.

  4. Configure the Resource path, Query String parameters, and authentication as necessary.
  5. In the Resource Methods step, specify the Resource name and select the desired Method, such as GET or POST.

  6. On Integration layer provide the Parent Class name and Connector name as shown below.

  7. Skip the Data Layer.

    You will see the following Final screen after generating Data Model:

    The Generated Data Model and API infrastructure looks as shown below:

  8. Extend the LoadFHIR4Settings DataTransform rule in your application layer and specify the end-point URLs of your source systems.
  9. Analyze PegaHC-Data- classes to identify existing logical data class to map the response data and/or create a new data class as needed.
  10. Create the appropriate Response Data Transform rules to map the response data to the appropriate Data class identified/created above. See MapToMembers4 and MapToMember4Details for reference.
  11. Create an appropriate Data Page (see example D_FHIR4Member) to call the configured REST service and the appropriate request and response Data Transform rules.

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