Define the clinical capability
Start with the knowledge or screening your users need: interactions, allergy and cross-reactivity, patient-specific considerations, duplicate therapy, or a consolidated assessment. Availability through a specific interface must be confirmed for your use case.
Understand the information exchange
An integration discussion should establish how medications are identified, which patient inputs are required, how findings are structured, and what supporting detail can be displayed. Your team should be able to distinguish completed screening from missing, unmatched, or unsupported inputs.
Evaluate before embedding
Review documentation for the available interface, agree synthetic test cases, and assess how your application will present clinical context and limitations. Confirm authentication, versioning, data handling, error behavior, and content licensing before deployment.
Discuss implementation requirements
Tell us about your system, clinical use case, target markets, and expected deployment. We will use this information to scope the evaluation and identify the documentation required.
Authentication and evaluation access
Access arrangements and authentication requirements must be confirmed for the interface under evaluation. Request the current technical documentation to review the supported access model. Do not send credentials through a website inquiry.