Developer guides · Updated September 14, 2026
Plan for interface changes
Agree on lifecycle expectations before an integration becomes operational.
Ask for the supported contract
Request the current API or tool version, any planned replacement and the notification channel for your evaluation environment.
Monitor notices
Check the release information and response metadata supplied by the service. An announced change should be assessed against your actual client behavior.
Test a migration
Use synthetic records to compare the current and replacement contract. Check authentication, field handling and change notifications before switching.
Confirm commitments in writing
No public support duration or deprecation notice period is promised by this website. Required timelines belong in the applicable agreement.
Keep moving
For an existing evaluation, email support@medicallibrarytech.com. Do not include credentials, patient information or confidential records.