MediBridgeX API v1.0

Introduction

Welcome to the MediBridgeX Developer Documentation. Our platform provides a suite of APIs for processing HL7v2 messages, validating FHIR R4 resources, and maintaining HIPAA-compliant cryptographic audit trails.

Base URL

All API requests should be prefixed with the following base URL. We recommend using HTTPS for all requests to ensure data encryption in transit.

https://api.medibridgex.com/v1

Authentication

The MediBridgeX API uses OAuth 2.0 Client Credentials flow for server-to-server communication. You can generate your API keys in the Developer Dashboard.

Generate Bearer Token
1curl -X POST https://api.medibridgex.com/v1/auth/token \
2  -H "Content-Type: application/json" \
3  -d '{
4    "client_id": "your_client_id",
5    "client_secret": "your_client_secret",
6    "grant_type": "client_credentials"
7  }'

Response Formats

The API exclusively returns JSON. All successful responses will have a 2xx status code, while errors will return 4xx or 5xx along with a standardized error object.

RESTful Design

Standard HTTP verbs (GET, POST, PUT, DELETE) are used to perform CRUD operations on FHIR resources.

Cryptographic Logs

Every mutation is automatically recorded in the HIPAA Audit Trail with an immutable SHA-256 signature.