5 Minute Setup

Quickstart Guide

Learn how to authenticate, send your first legacy HL7v2 message, and instantly receive standardized FHIR R4 resources back.

1Get your API Keys

Before making any requests, you need to generate your OAuth 2.0 Client Credentials. Navigate to your Developer Dashboard → API Keys and click "Generate New Secret". Use these credentials to request a Bearer token as shown in the Introduction.

2Send an HL7v2 Message

MediBridgeX acts as a universal translator. You can POST raw, pipe-delimited HL7v2 text directly to our ingestion endpoint. Our engine will automatically parse, map, and convert it.

Ingest HL7v2 ADT Message
1curl -X POST https://api.medibridgex.com/v1/messages/hl7 \
2  -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
3  -H "Content-Type: text/plain" \
4  -d "MSH|^~\&|SENDING_APP|SENDING_FAC|RECV_APP|RECV_FAC|20231027101530||ADT^A01|MSG00001|P|2.4
5PID|1||87453||Doe^John^A||19800101|M|||123 Main St^^Citytown^CA^90210"

3Receive FHIR R4

Instantly, the engine responds with a fully compliant FHIR R4 Transaction Bundle. The patient data has been cleanly extracted and mapped. Note that this action was automatically recorded in your HIPAA Audit Trail.

Response (200 OK)
1{
2  "status": "success",
3  "data": {
4    "resourceType": "Bundle",
5    "type": "transaction",
6    "entry": [
7      {
8        "resource": {
9          "resourceType": "Patient",
10          "id": "pat-87453",
11          "name": [
12            {
13              "family": "Doe",
14              "given": ["John", "A"]
15            }
16          ],
17          "gender": "male",
18          "birthDate": "1980-01-01"
19        }
20      }
21    ]
22  }
23}

What's Next?

Now that you understand the basic flow, you can explore our webhooks to receive data asynchronously, or dive deeper into the specific FHIR resources we support.