Medtimes Developers
Clinical Backend as a Service. Build the customer experience; connect to Medtimes for the governed clinical workflows behind it.
An API into care operations, not just a database
The intended partner flow is your application to the Medtimes API, then into Medtimes clinical operations. Internal teams coordinate the appropriate clinical service or physical fulfilment. Partners do not need to route directly to internal Matron or Hospital Admin tools.
For health products, employers and care partners
Use the developer platform to explore how a supported care request can fit into your existing product. Clinical scope, service availability, responsibilities and commercial terms must be agreed before a live integration.
Requests and connected updates
Explore supported care requests, correlation references and webhook updates. Consult the developer portal for the current API contract, onboarding requirements and the capabilities available to your integration.
Clinical responsibility remains explicit
An API key is not a clinical credential. Consent, authorised access, practitioner scope, record handling and escalation responsibilities must be defined for each integration. Treatment decisions remain with appropriately registered professionals.
Digital entry, physical follow-through
Medtimes is the clinical coordination layer. Doorstep Health supports physical fulfilment where required and available. Participating specialists, facilities and other providers retain their own professional responsibilities.
Your questions, answered
Is this just appointment-booking software?
The positioning is Clinical Backend as a Service: a connection into governed care workflows, not only a calendar. The capabilities available to a particular partner depend on its approved integration.
Can any app immediately offer every clinical service?
No. Production access, supported services, consent arrangements, responsibilities and capacity need to be confirmed during onboarding.
Where are the API documentation and access details?
Visit developers.medtimes.health for API documentation, partner access and the current supported integration workflows.
Medtimes is not an emergency service. Clinical decisions remain with appropriately registered professionals. Scope, cost and availability must be confirmed for your request.