How to integrate with ASP.MD
This page lists what ASP.MD publishes for integrations, from ONC's Certified Health IT Product List (CHPL) and ONC Lantern, as of 2026-11-11. Website: https://www.asp.md/.
Certified products
| Product | Latest version | Status | Certified | CHPL listing |
|---|---|---|---|---|
| ASP.MD Medical Office System | 92 | Active | 2022-02-03 | 15.02.05.1026.ASPM.01.01.0.220203 |
| ASP.MD Medical Office System (AMOS) | 92 | Retired | 2017-02-17 | 14.02.02.1026.A033.01.01.0.170217 |
Published API documentation
- Standardized API for Patient and Population Services (170.315 (g)(10)): https://fhirapi.asp.md:3030/aspmd/fhirserver/fhir_aspmd.asp
- Application Access - Patient Selection (170.315 (g)(7)): https://fhirapi.asp.md:3000
- Application Access - All Data Request (170.315 (g)(9)): https://fhirapi.asp.md:3000
FHIR endpoints
Service base URL list, which gives the FHIR endpoint for each customer: https://fhirapi.asp.md:3030/aspmd/fhirserver/endpoints.asp.
ONC Lantern tracks 1 FHIR endpoints for ASP.MD. 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.