Describe the workflow
Tell us what system will send or receive information and where clinician review sits in the flow.
Back to developers
Invitation-based integrations
Developer access starts with the clinical boundary.
Briefly does not publish generic credentials or a speculative interface. We first review the integration use case, the data flow and where clinician sign-off remains explicit.
Before access
No patient information belongs in an access request.
Describe the system, workflow and security requirements only.
Access review
Documentation follows a defined use case.
Review the data boundary
Confirm the data involved, required permissions, processing locations and retention expectations.
Receive current documentation
Approved integration teams receive the interface and security documentation that matches the current release.
Request the documentation that exists now.
Include your organisation, intended workflow and data-handling requirements. We will confirm whether the current integration surface is suitable.