Start collecting medical records in under 5 minutes
test
and live
. Test mode is used for development and testing, while live mode is used for production.
Test mode secret keys have the prefix private_test_
and live mode secret keys have the prefix private_live_
.
API Key Prefix | Description |
---|---|
public_test_ | Test mode client-side key that uniquely identifies your app |
private_test_ | Test mode server-side key allows you to make authenticated requests. Must be kept secret |
Create Credentials
button. You must provide a Redirect URL
, which is the URL that Fasten Connect will redirect the user to after they have successfully linked their account.
Create Webhook
button. You must provide a Webhook URL
, which is the URL that Fasten Connect will send events to.
public_test_123456324234234
with your own public key, which you can find
in the Developer Portal.
fasten-stitch-element
HTML element will render a button that your users can click to link their accounts to Fasten Connect.
test
mode, you can use the following credentials to test the Fasten Stitch component:
Test Credentials
Source | Credentials / Sandbox Status | Link |
---|---|---|
AdvancedMD | Username: Password: | |
Aetna | Username: VTETestUser01 Password: FHIRdemo2020 | test accounts |
AllScripts | Username: Password: | |
Anthem | Username: HOSPatient Password: HOSPatient2023 | |
AthenaHealth | Username: phrtest_preview@mailinator.com Password: Password1 | test accounts |
CareEvolution | Username: CEPatient Password: CEPatient2018 | test accounts |
Cerner | Username: nancysmart Password: Cerner01 | test accounts |
Cigna | Username: syntheticuser05 Password: 5ynthU5er5 | test accounts |
DynamicHealthIT | Username: Password: | |
eClinicalWorks/Healow | Username: AdultFemaleFHIR Password: e@CWFHIR1 | test accounts |
Epic | Username: fhircamila Password: epicepic1 | test accounts |
Flatiron/OncoEMR | Username: Password: | |
HealthIT | Username: demouser Password: Demouser1! | test accounts |
Humana | Username: HUser00001 Password: PW00001! | |
Kaiser | Username: Pvaluser1 Password: V@lidation1 | |
Logica | Username: Password: | |
MaximEyes | Username: Password: | |
Medhost | Username: Password: | |
Medicare | Username: BBUser00000 Password: PW00000! | test accounts |
Meditech | Username: Password: | |
Netsmart | Username: Password: | |
NextGen | Username: patientapitest Password: Password1! | test accounts |
PracticeFusion/PatientFusion | Username: Password: | |
VA Health | Provider: ID.me Username: va.api.user+101-2024@gmail.com Password: Password12345!!! | test accounts |
fasten-stitch-element
will generate a javascript event containing
information about connection. This payload will contain a org_connection_id
identifier that
you can use to make requests to the Fasten Connect API.
eventBus
event listener in the code snippet above.
data.org_connection_id
fields by sending it to your backend, as it is required for subsequent requests
to the Fasten API to request medical records for this individual patient.
You may also want to store the other fields for future reference, such as endpoint_id
, brand_id
, portal_id
and platform_type
.
/bridge/fhir/ehi-export
endpoint with the org_connection_id
of the patient whose records you want to export.
/bridge/fhir/ehi-export/{org_connection_id}
endpoint to check the status of the export./bridge/fhir/ehi-export
endpoint must be authenticated with your private key. Here’s an example using curl
:
POST
a webhook event to the URL you provided when creating the webhook.
The event will contain the task_id
and the download_link
of the export that was completed.
download_link
to download the export. The export will be a JSONL file
containing the patient’s medical records in FHIR format.