generated: '2026-08-14'
method: searched
source: >-
  https://docs.connect.fastenhealth.com/changelog,
  https://docs.connect.fastenhealth.com/support,
  https://status.fastenhealth.com/,
  https://docs.connect.fastenhealth.com/webhooks/events,
  https://docs.connect.fastenhealth.com/stitch/v4/sdks/web-component/quickstart,
  api.github.com/orgs/fastenhealth,
  openapi/fasten-health-connect-openapi-original.yml

versioning:
  scheme: uri-path
  current: v1
  spec_version: 1.0.11
  base_url: https://api.connect.fastenhealth.com/v1
  docs: https://docs.connect.fastenhealth.com/api-reference/introduction
  client_track:
    name: Stitch.js
    current: v4
    supported: [v4]
    maintenance_mode: [v1, v3]
    maintenance_note: >-
      The v1 and v3 Web Components are in maintenance mode and will receive security fixes only.
      v4 is documented as backwards compatible with v3 with no breaking public-API changes.
    docs: https://docs.connect.fastenhealth.com/stitch/v4/introduction

status_page:
  url: https://status.fastenhealth.com/
  http_status: 200
  linked_from: https://docs.connect.fastenhealth.com/support

sla:
  published: false
  note: >-
    The support page states that Service Level Agreements and Business Associate Agreements are
    "available for customers on upgraded plans". No uptime target, credit schedule or SLA document
    is published publicly.
  source: https://docs.connect.fastenhealth.com/support

support:
  channels:
    - {kind: docs, url: https://docs.connect.fastenhealth.com/support}
    - {kind: email, value: support@fastenhealth.com}
    - {kind: slack, note: shared Slack channel offered for real-time assistance}
    - {kind: api, operation: POST /support/request, note: file a support ticket through the API}
  ask_for: [organization_id, request_id]

deprecation:
  policy_url: https://docs.connect.fastenhealth.com/changelog
  policy_style: changelog-announced
  sunset_header: false
  deprecation_header: false
  note: >-
    There is no standalone deprecation-policy page and no RFC 8594 Sunset/Deprecation header
    support. Deprecations ARE announced with a named removal window in a dedicated "Deprecated"
    section of the dated changelog, and deprecated fields are additionally flagged in the reference
    docs, so the practice exists even though the policy is not written down.
  announced:
    - item: download_link (patient.ehi_export_success webhook field)
      announced: '2025-10-19'
      removal_target: '2026-06'
      replacement: download_links[]
      status: >-
        Still present and still flagged deprecated in the event reference as of 2026-08-14, past
        the stated June 2026 removal window.
    - item: org_connection_id as the identifier for EHI-Export status/download calls
      announced: '2024-09-30'
      removal_target: '2024-01'
      replacement: task_id
      status: >-
        The stated removal date precedes the announcement date; this appears to be an error in the
        changelog entry. The replacement (task_id) is what the current OpenAPI path parameters use.

deprecated_operations: []
deprecated_operations_note: >-
  No operation in the published OpenAPI 1.0.11 carries `deprecated: true`. Deprecation is expressed
  at the field level in the webhook docs instead.

open_source_lifecycle:
  note: >-
    DECAY SIGNAL — the company's flagship open-source product is archived. This is the single most
    consequential lifecycle fact in this profile and it is not reflected in the marketing site.
  repos:
    - name: fasten-onprem
      url: https://github.com/fastenhealth/fasten-onprem
      stars: 2795
      archived: true
      last_push: '2026-02-13'
      last_release: v1.1.3 (2024-10-01)
      note: >-
        The self-hosted personal/family EMR that the company was founded on is ARCHIVED (read-only)
        on GitHub. Verified via api.github.com/repos/fastenhealth/fasten-onprem on 2026-08-14.
    - name: fasten-toolbox-api
      url: https://github.com/fastenhealth/fasten-toolbox-api
      archived: true
      last_push: '2024-10-06'
    - name: fasten-answers-ai
      url: https://github.com/fastenhealth/fasten-answers-ai
      archived: false
      last_push: '2024-10-31'
      note: Proof-of-concept, dormant for ~22 months.
    - name: fasten-stitch-element-flutter
      url: https://github.com/fastenhealth/fasten-stitch-element-flutter
      archived: false
      last_push: '2026-08-08'
      status: alpha
      note: Self-described "[ALPHA] Work-in-progress"; not published to pub.dev and not yet in the docs.
  active: >-
    Commercial-side repos remain active — cdn, fasten-connect-stitch-embed-prod, the Stitch React
    and React Native SDKs, gofhir-models and folio all saw pushes in 2026. The archive is confined
    to the original self-hosted product line.

host_changes:
  - change: Developer Portal domain migration
    date: '2026-08-04'
    from: portal.connect.fastenhealth.com
    to: portal.fastenhealth.com
    source: https://docs.connect.fastenhealth.com/changelog
    note: >-
      Announced in the changelog with a recommendation to update bookmarks. Both hosts answered 200
      on 2026-08-14. apis.yml has been updated to the new domain.
  - change: Documented identity host does not resolve
    host: identity.fastenhealth.com
    finding: >-
      The Bring Your Own Identity guide documents POST https://identity.fastenhealth.com/oauth2/par
      and GET https://identity.fastenhealth.com/jwks.json as production endpoints, but the hostname
      returns NXDOMAIN in public DNS and every probe failed to connect (curl exit 6, status 0) on
      2026-08-14. Either the surface is not yet live, or it is only resolvable to onboarded TEFCA
      subparticipants via split-horizon DNS. Recorded as observed, not interpreted.

changelog:
  url: https://docs.connect.fastenhealth.com/changelog
  entries: 72
  span: 2024-09-30 .. 2026-08-04
  artifact: changelog/fasten-health-changelog.yml