Why does this integration require two different API calls?

MediRecords architecture separates the consultation structure from the content. Phase 1 uses the FHIR API to create the encounter, and Phase 2 uses the REST API to append the clinical notes.

Are the authentication tokens for FHIR and REST APIs identical?

No. Phase 1 requires a FHIR-specific token, while Phase 2 requires a separate REST token. Using the incorrect token type for either phase will result in an authentication failure.

What causes the HTTP 409 error during encounter creation?

An HTTP 409 error typically occurs if the encounter status is set to 'in-progress'. The API requires the status to be 'finished' to successfully create the record in this workflow.

Can I edit or replace SOAP notes after they have been appended?

The current MediRecords API only supports appending notes to a consultation. There is no existing endpoint to edit or replace notes once they have been submitted via the REST API.

MediRecords EHR Integration

Name: MediRecords EHR Integration
Author: adaptationio

byadaptationio

API Development

Standardizes the two-phase integration process for saving AI consultations and SOAP notes into the MediRecords EHR system.

About

This skill provides a technical framework for developers integrating medical software with the MediRecords platform. It specifically solves the complexity of the required two-phase consultation workflow: initiating encounters through the FHIR API and appending clinical SOAP notes via the REST API. By providing validated code snippets, precise authentication requirements, and a comprehensive troubleshooting guide for common HTTP status errors, it ensures that AI-generated clinical documentation is securely and accurately synced with patient records.

Key Features

Verified boilerplate for patient searching and HTML SOAP note formatting
Two-phase workflow for FHIR Encounter creation and REST note appending
Detailed troubleshooting for common HTTP 409, 500, and 400 error codes
Automated integration test scripts for verifying UI visibility and data integrity
Clear mapping of FHIR vs. REST authentication token requirements
0 GitHub stars

Use Cases

Implementing patient record lookups and ambulatory care documentation workflows
Automating the transfer of AI-generated SOAP notes to MediRecords patient files
Debugging synchronization issues between FHIR encounters and REST clinical notes

About

Key Features

Verified boilerplate for patient searching and HTML SOAP note formatting
Two-phase workflow for FHIR Encounter creation and REST note appending
Detailed troubleshooting for common HTTP 409, 500, and 400 error codes
Automated integration test scripts for verifying UI visibility and data integrity
Clear mapping of FHIR vs. REST authentication token requirements
0 GitHub stars

Use Cases

Implementing patient record lookups and ambulatory care documentation workflows
Automating the transfer of AI-generated SOAP notes to MediRecords patient files
Debugging synchronization issues between FHIR encounters and REST clinical notes