Build with AI

You have access to the Scan.com Partner API v2 documentation:
- Full docs: https://docs.scan.com/llms-full.txt
- Page index: https://docs.scan.com/llms.txt
- OpenAPI: https://docs.scan.com/openapi.yaml
Use the sandbox host https://api.staging.scan.com/api/v2 only.
Authenticate with "Authorization: Bearer $SCAN_API_TOKEN" and read the token from the environment.
Consult these before writing any Scan.com integration code.

Using the Scan.com Partner API v2 sandbox, write a script in <language> that takes one synthetic patient from referral to booking.

Read first:
- https://docs.scan.com/guides/quickstart.md
- https://docs.scan.com/guides/submit-a-medical-referral.md
- https://docs.scan.com/guides/submit-medical-questions.md
- https://docs.scan.com/guides/submit-preferred-times.md
- https://docs.scan.com/guides/submit-a-booking.md
- https://docs.scan.com/openapi.yaml

Steps, in order:
1. POST /testing/fixtures and keep cpt_code_id, icd10_code_id, and body_part_id.
2. POST /referrals with order_form (PDF data URL), injury_type, incident_date, patient, and visits[].orders[].cpt_code_id.
3. GET then PUT /referrals/{referral_id}/medical_questionnaire.
4. POST /referrals/{referral_id}/scheduling_preferences.
5. POST /referrals/{referral_id}/book.
6. GET /referrals/{referral_id} and print visits[].status.

Rules:
- Base URL https://api.staging.scan.com/api/v2, token from SCAN_API_TOKEN.
- Use ids from /testing/fixtures. Do not hardcode catalog ids.
- Do not send a modality string. cpt_code_id infers it.
- On an error, log type, code, and request_id. Do not retry 4xx.

Build a webhook endpoint in <language/framework> for Scan.com Partner API v2 events.

Read first:
- https://docs.scan.com/guides/webhooks.md
- https://docs.scan.com/webhooks/status-changed.md
- https://docs.scan.com/guides/testing-and-sandbox.md

Requirements:
- Read the raw body before parsing JSON.
- Verify X-Scan-Signature: HMAC-SHA256 of "<timestamp>.<raw_body>" with the signing secret. The header can hold several v1= values during rotation; accept a match on any of them.
- Reject timestamps older than five minutes.
- Route on X-Scan-Event: visit.status_changed, notification.status_changed, referral.auto_book_completed.
- Dedupe visit and notification events on event_id. Make auto-book handling idempotent on auto_book_request.id and its terminal status.
- Delivery is at least once and not ordered. After an event, GET the referral and treat visits[].status as the source of truth.
- Return 2xx quickly and do the work in a background job.
- Test with POST https://api.staging.scan.com/api/v2/testing/events and {"event_name":"visit.status_changed"}.

Add Scan.com referral status tracking to my <language> integration.

Read first:
- https://docs.scan.com/guides/track-referral-status.md
- https://docs.scan.com/guides/objects.md
- https://docs.scan.com/guides/testing-and-sandbox.md

Requirements:
- Key integration logic off visits[].status, not the top-level referral status.
- Act on the milestones the guide lists, and ignore statuses you do not recognize, because new ones can be added.
- Store the latest status per visit and skip updates that are not newer.
- Write a sandbox test that moves a fixture visit with PATCH /testing/visits/{visit_id} through booked, report_uploaded, and sent_to_rp, and asserts the handler for each.

Write a <language> function that downloads the report, DICOM study, and invoice for a Scan.com visit.

Read first:
- https://docs.scan.com/guides/order-documents-and-dicom.md
- https://docs.scan.com/openapi.yaml

Requirements:
- Use GET /order_documents and the dedicated report, dicom, and invoices routes.
- Pass delivery=url. Base64 delivery is deprecated and large studies are not expanded.
- The URL expires after 15 minutes, so download right away and never store the URL.
- Treat a missing document as "not ready yet", not an error. DICOM returns 404 when the study is missing.

Add an HTTP client wrapper in <language> for the Scan.com Partner API v2.

Read first:
- https://docs.scan.com/guides/errors.md

Requirements:
- Parse the error envelope: type, code, message, request_id, documentation_url, and errors when present.
- Log the X-Request-Id header on every response.
- Raise one exception class per type: authentication_error, validation_error, permission_error, not_found_error, rate_limit_error, api_error.
- Retry only 5xx and 429, with exponential backoff and jitter. Never retry other 4xx.
- Include request_id in the exception message so support can find the call.

This integration is for workers' compensation. Read https://docs.scan.com/guides/lines-of-business/workers-comp-and-payers.md and apply its required fields and call order. After the referral leaves pending or canceled, poll GET /referrals/{referral_id}/payments. An empty referral_payments array is normal until Scan logs a payment.

This integration is for an employer benefit team. Read https://docs.scan.com/guides/lines-of-business/employers-and-benefit-teams.md and apply its required fields and status handling.

This integration is for a health plan. Read https://docs.scan.com/guides/lines-of-business/health-plans.md and apply how health-plan referrals appear on GET and in webhooks.