Developer guides · Updated September 14, 2026
Version the things your client depends on
Content versions, sample versions and interface versions answer different questions.
Published content version
A content version identifies a particular published result. Your client should preserve the identifier needed to explain which result it used.
Interface and schema version
Confirm the supported routes, schema and compatibility rules for your evaluation environment. Historical API documentation is not a guarantee of the current deployment contract.
Public sample version
The downloadable fixture uses sample_version 1.0. This labels the educational fixture only. Its fields are illustrative and are not a production API schema.
Before a rollout
Test known responses, missing fields and correction behavior. Record the approved contract version and ask how changes will be communicated.
Keep moving
For an existing evaluation, email support@medicallibrarytech.com. Do not include credentials, patient information or confidential records.