Access and permissions
Agree on authentication, credentials and access limits before implementing the integration.
Explore integration possibilities and present your project. API access starts with a clear scope and approval from our team.
Explore connection points. Features, documentation and access terms are confirmed for each project.
Assess how to connect patient records and identification to your product, with fields and permissions defined for the project.
Purpose, data and permissions must be part of the project from the start.
Agree on authentication, credentials and access limits before implementing the integration.
Define the purpose, minimum data and each party's responsibilities.
Agree on validation scenarios, failure handling and monitoring.
Present your product, organization and integration purpose.
Our team assesses availability, documentation and permissions.
Agree on technical requirements and validation scenarios.
Use is subject to approval and agreed terms.
Provide your company, integration objective and required data. After reviewing the project, our team will guide you on applicable documentation and access approval.
Submitting does not automatically grant API access. Do not include credentials or patient data.
No. Present your project through this page's form. Our team will explain access terms after assessment.
Applicable documentation is agreed with the team according to the integration's approved features and permissions.
No. Requests are subject to scope assessment, availability and usage terms. Submitting the form grants neither credentials nor data access.