Connection and test

Step 2 of 7. Enter the address and credentials, then test.

This screen answersDS-2

Acceptance criteria

DS-2 Plugins, connection and credentials P1 ADDED BY SCOPE: DATA SOURCES NEW SCREEN

As a Super admin, I need to install a connector plugin and test the connection, so I know the hospital system answers before anything depends on it.

A plugin is a way to reach a source: REST or FHIR API, SQL database, HL7 feed, file drop (SFTP or CSV) or a vendor plugin. The catalog shows installed and available plugins.
Credentials are masked after saving and live in a vault, never in the portal database. Test connection shows what was reached, how fast and what failed.

Wireframe state

DefaultTest okTest failed

Step 2 of 7

Connection and test

Enter the address and credentials of the hospital system, then test it.

Connection

Name

Base URL

Authentication

Client id

Client secret

Saved in the secrets vault. Shown masked from now on.

Timeout

Test connection

Result

Not tested yet. Enter the connection and choose Test connection.

Connection works. Reached in 212 ms. FHIR version 4.0.1. 5 resources found: Patient, Practitioner, Organization, Coverage, Location.

Test failed. The certificate of fhir.alraneem-hospital.example expired on 03 Oct 2026.

Likely causes

Certificate expired (this one)
401: the client secret was rotated
Timeout after 30 seconds: the address is blocked

Next steps

Ask the hospital IT team to renew the certificate.
Test again.
Until then, the entities keep their last known data.

Secrets stay in the vault. Secrets are stored in the secrets vault, never in the portal database. After saving, nobody can read them back, only replace them.

Cancel setupBackNextNext