Public FHIR definitions
Trévor's code systems, extension and questionnaires are published read-only under https://trevor.coachdrepa.no/fhir/, with no authentication and no health data.
Developers
Trévor interoperability: FHIR, SMART on FHIR and the data model.
This page gathers what an institution, a patient-record vendor or a developer can use or check. Trévor exposes no public health-data API: every piece of data stays under the control of the person concerned, who links or unlinks their own records.
Export conforming to Swiss profiles
The FHIR R4 export follows CH Core 6.0.0 with SNOMED CT, LOINC and UCUM. The official HL7 validator reports no error on a multi-diagnosis sample record.
SMART on FHIR connectors
Authorisation by the person (PKCE), incremental reading and sending of the follow-up to Epic, the HUG patient record system or any FHIR R4 server, and to the electronic patient record through IHE MHD and PIXm.
Documented data model
The diagrams below are generated from the code of Trévor 2.150.6: a change to the tables or to the diagnosis profiles updates them with the next release.
Public endpoints
Base URL of the FHIR definitions: https://trevor.coachdrepa.no/fhir. Pour /health et /.well-known, l'adresse de base est https://trevor.coachdrepa.no. Réponses en JSON FHIR, lecture seule.
| Path | Content |
|---|---|
/fhir/metadata | CapabilityStatement: what Trévor publishes |
/fhir/CodeSystem/{id} | Local code systems (trevor-item, trevor-answer, wearable-metric, prevention-exam, self-report, diagnosis-role) |
/fhir/StructureDefinition/{id} | Diagnosis role extension (primary, secondary) |
/fhir/Questionnaire/{id} | The follow-up questionnaires, one per identifier |
/.well-known/jwks.json | Trévor's public key for signed exchanges with an institution (published once a key is configured) |
/health | Service status and version |
Data model
Each diagram opens as SVG; the Mermaid source is published alongside.
FHIR export
Connectors to health records
Connectors stay switched off until an institution has agreed its access: each one needs an agreement and an application identifier. Latest check run against public test servers:
| Check | Status |
|---|---|
| SMART discovery, Epic sandbox | Passed |
| Epic organisation directory | Passed |
| Full SMART flow (SMART Health IT launcher) | Passed |
| Send, read back and delete a record (HAPI FHIR) | Passed |
| Epic authorisation with a test patient | Not run: access required |
| PIXm and MHD (test EPR) | Not run: access required |
Preparing a connectathon, an integration or a conformance check? Write to the team: we share the technical detail, the profiles used and the validation results.