4. Test your FHIR API endpoint
After you get configuration verification from your EHR vendor (as previously described), you’re able to run the FHIR API endpoint test. This automated test checks the availability of your FHIR API endpoint and its test patient data.
Note: When the FHIR API endpoint is published, Apple performs routine monitoring of the FHIR API endpoint by testing it several times a day. If Apple detects errors, your administrative and technical contacts will receive emails about the issues.
Go to the FHIR API Profile screen for the endpoint.
Click Start Test.
The test should finish within a few minutes.
Do one of the following:
If the test is successful: Click Send for Review, then see Await your application review.
If the test is not successful: Click View Test Results, address the reported issues, return to the FHIR API Profile screen, then click Start Test to repeat the test. Continue the testing cycle until there are no more issues.
Failures: These errors must be corrected before you’re allowed to publish the FHIR API endpoint in the Health app. Failures are usually caused by the URLs not being available, a missing client ID or refresh token, missing or incorrect information in FHIR resources, incorrect test patient credentials, or other network and API configuration issues that prevent Apple from connecting to your FHIR API endpoint. Consult with your EHR vendor if you’re unable to correct the errors.
Recommendations: These errors won’t prevent you from publishing the endpoint on the Health app. However, you should address them to ensure the best experience for your patients.
If the Health Records Directory Listing Agreement hasn’t been accepted by your organization’s signing authority: Click View Agreement, then either accept the agreement or follow up with your signing authority about accepting the agreement. The test results don’t appear until Apple receives acceptance of this agreement. (See Respond to the Health Records Directory Listing Agreement.)