Life Sciences & Pharmaceuticals

Medical Information Response Assistant

Designed for Medical information specialist

Answer unsolicited medical information enquiries from healthcare professionals with on-label, referenced responses drawn from approved documents, escalating off-label or adverse-event content to a qualified reviewer.

Contract LIF-03 · primary aggregate EnquiryCase · mode loading

Decision brief

Medical review and release: evidence ready for review

This brief starts with the decision, evidence, and accountable owner. The guided workflow then shows how the recommendation was produced.

Decision signals

The evidence and control points that shape this recommendation.

Decision owner

Qualified medical reviewer

The named role remains accountable for the consequential decision.

Governed evidence

5 record types

Structured records and cited text ground the recommendation.

Workflow

5 controlled stages

Each transition records its input, output, status, and audit context.

Human controls

1 approval gate

Approval gates prevent the copilot from making consequential decisions.

Business problem

A cardiologist asks about dosing in severe renal impairment for a product whose local label is silent; the assistant finds no on-label statement, retrieves a cleared pharmacokinetic publication, segments that content as off-label, and holds the reply until a qualified medical reviewer approves the wording and confirms no adverse event was reported..

Decision to make

Answer unsolicited medical information enquiries from healthcare professionals with on-label, referenced responses drawn from approved documents, escalating off-label or adverse-event content to a qualified reviewer.

Outcome to show

Released response and archived enquiry record gives Qualified medical reviewer the evidence needed to begin the final governed business outcome, with the decision trail retained for review.

  1. 1Capture and classify the enquiry
  2. 2Screen for adverse events and product complaints
  3. 3Retrieve approved responses and label scope
  4. 4Draft the referenced reply
  5. 5Medical review and release

Step 1 of 5

Ready: Start with the business question, then use the single button above.

The output appears here immediately. More technical evidence remains available below.

System logic, GenAI, and human accountability

The demonstration keeps deterministic controls, AI assistance, and approval separate.

System logic

Source systems enforce identity, workflow order, policy filters, and record updates.

GenAI contribution

Retrieval and generation assemble relevant evidence into a cited recommendation or draft.

Human accountability

Qualified medical reviewer verifies material claims and approves the consequential action.

Workflow stages

Run the stages in order before using the Copilot. Every stage explains what happens, why it matters, the evidence it uses, and the complete API request and response.

Seeded record
Loading
Document type
Loading
Container
Loading
Partition key
Loading
Current stage
Loading

API demonstration guidance

Run a stage to see its explanation, evidence, full request, and full response.

Grounded chat

Ask a question and receive an answer grounded in retrieved EnquiryCase evidence.

Answer and evidence

Select a starter question or enter your own.

Evidence

Domain implementation workspace

Loaded live from /api/config, /api/domain/model, and /api/domain/sample.

Domain objective
Answer unsolicited medical information enquiries from healthcare professionals with on-label, referenced responses drawn from approved documents, escalating off-label or adverse-event content to a qualified reviewer.
Primary aggregate
EnquiryCase
Primary container
enquiryCases
Hierarchical key
/tenantId + /enquiryId
Schema version
1

Sample scenario

A cardiologist asks about dosing in severe renal impairment for a product whose local label is silent; the assistant finds no on-label statement, retrieves a cleared pharmacokinetic publication, segments that content as off-label, and holds the reply until a qualified medical reviewer approves the wording and confirms no adverse event was reported.

Physical Cosmos DB containers

Every container provisioned for this accelerator with its hierarchical partition key.
Container Role Hierarchical partition key Document types
enquiryCases Primary /tenantId + /enquiryId EnquiryCase, ResponseDraft
medicalContentLibrary Reference /tenantId + /contentDocumentId ApprovedResponseDocument, ProductLabelSection, PublicationReference

Document types

Contract document types, their owning container, and their identifier pattern.
Type Container Partition key Identifier pattern Embedding fields
EnquiryCase enquiryCases /tenantId + /enquiryId enquiry::{enquiryId} enquiryTextVector
ApprovedResponseDocument medicalContentLibrary /tenantId + /contentDocumentId standardresponse::{contentDocumentId}::{chunkIndex} bodyVector
ProductLabelSection medicalContentLibrary /tenantId + /contentDocumentId label::{contentDocumentId}::{countryCode}::{sectionCode} sectionVector
PublicationReference medicalContentLibrary /tenantId + /contentDocumentId publication::{contentDocumentId} abstractVector
ResponseDraft enquiryCases /tenantId + /enquiryId response::{enquiryId}::{draftVersion} responseVector

Query patterns