How to integrate with Advanced Data Systems
This page lists what Advanced Data Systems publishes for integrations, from ONC's Certified Health IT Product List (CHPL) and ONC Lantern, as of 2026-11-11. Website: https://www.adsc.com.
Certified products
| Product | Latest version | Status | Certified | CHPL listing |
|---|---|---|---|---|
| MedicsCloud | 11.0 | Active | 2022-01-11 | 15.02.05.1044.AVDC.01.01.1.220111 |
| MedicsDocAssistant | 8.0 | Active | 2022-01-11 | 15.02.05.1044.AVDD.01.01.1.220111 |
Published API documentation
- Standardized API for Patient and Population Services (170.315 (g)(10)): https://fhir.medicscloud.com/docs/MedicsCloud-FHIR-API.htm
- Standardized API for Patient and Population Services (170.315 (g)(10)): https://fhir.medicscloud.com/docs/MedicsDocassistant-FHIR-API.htm
- Application Access - Patient Selection (170.315 (g)(7)): https://staging.medicscloud.com/MCExtAPI/Home/Help
- Application Access - Patient Selection (170.315 (g)(7)): https://staging.medicscloud.com/MedicsDAExtAPI/Home/Help
- Application Access - All Data Request (170.315 (g)(9)): https://staging.medicscloud.com/MCExtAPI/Home/Help
- Application Access - All Data Request (170.315 (g)(9)): https://staging.medicscloud.com/MedicsDAExtAPI/Home/Help
FHIR endpoints
Service base URL list, which gives the FHIR endpoint for each customer: https://fhir-service.medicscloud.com/r6/DA/get-clients-end-points, https://fhir-service.medicscloud.com/r6/mc/get-clients-end-points.
ONC Lantern tracks 1 FHIR endpoints for Advanced Data Systems. Reported FHIR versions: 4.0.1 (1).
How to integrate
- Read the (g)(10) documentation above. ONC criterion 170.315(g)(10) requires a standardized FHIR API for patient and population services.
- Register your application with the vendor, as its documentation describes.
- Authorize with SMART App Launch, or with SMART Backend Services for system-to-system access.
- Find the practice's FHIR base URL in the service base URL list.
- Plan for the gaps. (g)(10) certifies read access to USCDI data. Scheduling, charges, claims and write-back need vendor-specific APIs or another route.