Skip to main content

2 posts tagged with "features"

View All Tags

Postman Integration

· 2 min read
Confused-Moniker
Maintainer of IGUHealth

Postman is a platform that allows you to use APIs with a user-friendly interface. It can be a great way to test your API endpoints and check for conformance and data quality. This guide will cover how to integrate with Postman.

How to integrate Postman with Iguhealth

Download Postman

  1. Download Postman from the official website.

Setup IGUHealth

  1. Go to the admin application and create a new ClientApplication.
  2. Set the name to Postman
  3. Set the grant type to client_credentials.
  4. Set the response type to token.
  5. Set the secret to a secure value.
  6. Hit Actions and create
  7. Mark down the client ID and secret.
  8. Click Security->AccessPolicyV2 in the admin app and create a new access policy.
  9. Create AccessPolicyV2 with the engine set to `Full Access'.
  10. Under Target.Link reference the ClientApplication created on step 5.

Authorize Postman

  1. Open Postman and create a new request.
  2. Under Authorization set type to OAuth 2.0.
  3. Under Configure New Token set Grant Type to Client Credentials.
  4. Set ClientID and ClientSecret to the values from step 7.
  5. Set the Access Token URL to value at User -> Settings -> Endpoints -> Security -> Token
  6. Click Get New Access Token and confirm that you get an access token.

Test

  1. Get R4 endpoint from User -> Settings -> Endpoints -> FHIR -> R4
  2. Make get requests in Postman to the ${r4Endpoint}/metadata
  3. Confirm that you get a 200 response with CapabilityStatement in body.

Vanya Client Integration

· 3 min read
Confused-Moniker
Maintainer of IGUHealth

Vanya client is a desktop app that allows you to view data in FHIR. It works with a variety of FHIR servers and can be a great way to check for conformance and data quality more on that later.

How to integrate Vanya with Iguhealth

OAuth Client Credentials

  1. Go to the admin application and create a new ClientApplication.
  2. Set the grant type to client_credentials.
  3. Set the response type to token.
  4. Set the secret to a secure value.
  5. Hit Actions and create
  6. Mark down the client ID and secret.
  7. Click Security->AccessPolicyV2 in the admin app and create a new access policy.
  8. Create AccessPolicyV2 with the engine set to `Full Access'.
  9. Under Target.Link reference the ClientApplication created on step 5.
  10. Open the Vanya client.
  11. Click Add New Server.
  12. Go to Settings on the Admin App and copy the FHIR R4 URL.
  13. Paste the URL in the Vanya Client for the URL.
  14. In Vanya, click OAuth2.
  15. Copy and paste the token endpoint from the admin app settings.
  16. Copy the clientID from step 5 and paste it in Vanya.
  17. Copy the client secret from step 5 and paste it in Vanya.
  18. Set the grant type to client_credentials.
  19. Click Save.

Basic Authentication

  1. Go to the admin application and create a new ClientApplication.
  2. Set the grant type to basic_auth.
  3. Set the response type to token.
  4. Set the secret to a secure value.
  5. Hit Actions and create
  6. Mark down the client ID and secret.
  7. Click Security->AccessPolicyV2 in Admin App and create a new access policy.
  8. Create AccessPolicyV2 with the engine set to `Full Access'.
  9. Under Target.Link reference the client application created on step 5.
  10. Use the below widget and enter the client ID and secret, then copy the authorization header value.

Below is a simple form to generate an Authorization header for basic authentication.

  1. Open the Vanya client.
  2. Click Add New Server.
  3. Click the Request Headers tab, create a key Authorization and paste in the value from step 10.
  4. Go to Settings on the Admin App and copy the FHIR R4 URL.
  5. Paste the URL in the Vanya Client for the URL.
  6. Click Save.

Vanya Client discovered a non-conformant aspect of our server

We use nanoid to generate unique identifiers for our resources. Vanya client discovered that our use of the default alphabet for nanoid, is not FHIR compliant. Specifically the _ is a character not allowed in FHIR ids.