Api Bronson _top_ File

Include in every request: Authorization: Bearer <access_token> 3. Core Endpoints | Resource | Method | Endpoint | Description | |------------------|--------|------------------------------|-------------| | Patient lookup | GET | /patients/id | Get patient by ID | | Search patients | GET | /patients?last=Smith&dob=1970-01-01 | Search | | Create appointment| POST | /appointments | Book new appointment | | List appointments | GET | /appointments?patient_id=id | Upcoming visits | | Clinical notes | GET | /patients/id/notes | SOAP notes, summaries | | Lab results | GET | /patients/id/labs | Recent lab results | 4. Example Requests 4.1 Get Patient by MRN curl -X GET "https://api.bronson.io/v1/patients/MRN-10045" \ -H "Authorization: Bearer YOUR_TOKEN" \ -H "Accept: application/json" Response:

All errors return standard HTTP status codes with a JSON body: api bronson

https://api.bronson.io/v1 (sandbox: https://sandbox-api.bronson.io/v1 ) Version 1

"error": "invalid_request", "message": "Missing required field: patient_id", "status": 400 "message": "Missing required field: patient_id"

If you have a specific Bronson API (e.g., Bronson Healthcare, Bronson Labs), this guide gives you a template to adapt. Version 1.0 | REST | JSON | OAuth 2.0 1. Overview API Bronson provides programmatic access to patient records, scheduling, clinical data, and billing information. It follows REST principles and uses standard HTTP methods.

"id": "MRN-10045", "first_name": "Jane", "last_name": "Doe", "dob": "1985-06-15", "gender": "F", "phone": "+1234567890", "email": "jane.doe@example.com"