Molecular Diagnostics
Regulated development and commercialization journeys where clinical, quality, and market access align.
This interactive experience is the shipped product itself — the same application code customers run in production, mounted read-only in your browser over a real sample journey. Not a video, not a mockup: because the demo and the product are one codebase, it can never drift from the real thing.
Inside this journey
-
Clinical Needs Discovery
Align on clinical goals, current lab workflows, staffing, space constraints, validation requirements, and measurable success signals for molecular testing.
Discovery Questions
Start Here — Your current molecular testing picture
- How many molecular tests does your lab run on an average weekday?
- Which sample types (for example, nasopharyngeal swabs, blood culture, tissue) are you running most often on those assays?
- Tell me which instrument classes currently handle your rapid molecular testing and approximate daily throughput per class
- In a typical month, how many samples require same-day or within-6-hour reporting?
- Who on your team currently owns molecular validation and ongoing QA activities?
- Describe your current staffing model for molecular work, including number of FTEs trained in molecular techniques and their typical shift coverage.
- Has your lab secured capital approval or an approved budget line for a new molecular instrument this fiscal year?
Where slowdowns cost patients and budgets
- If a delayed molecular result leads to a one-day longer hospitalization for a typical patient, estimate the additional cost per case to your institution.
- How often do instrument downtime or reagent backorders cause turnaround times to exceed your clinical targets?
- Which step in your current workflow creates the most hands-on time per sample?
- When a new assay fails initial validation, who makes the go/no-go call and on what criteria?
- Provide an example of a recent case where a slower molecular result changed clinical treatment, and the downstream consequence.
- If regulatory or payer pressures required same-day reporting for a new panel, would that make you move forward with a new platform within 3 months?
How samples actually move through your lab on a busy day
- Walk me through the last time a STAT sample arrived, from accessioning to result reporting, and where the clock slipped.
- On average, how long does accessioning, extraction, amplification, and reporting take today for a typical syndromic panel?
- List the LIS or middleware messages that are automated versus manual in your current result flow.
- Who gets alerted when a critical positive result posts, and how quickly do clinical teams receive that notification?
- Describe any manual reconciliation steps required between instrument output and patient chart before sign-out.
- Identify the single operational constraint that, if unresolved, would prevent deployment within your target window.
Validation and quality, the gatekeepers of go-live
- Name the validation milestone in your process that has the highest chance of failure and would delay go-live.
- Estimate the number of full clinical runs you require for internal verification before clinical use.
- List the roles that must sign the validation report for the new assay to be accepted into routine testing.
- Provide the typical acceptance criteria thresholds you use for sensitivity, specificity, and limit of detection.
- Would the requirement for matrix-specific validation without available residual specimens be sufficient to stop approval?
- State the frequency at which you run internal QC for molecular runs during routine operations.
Alternatives you're weighing and their real chances
- Outline the alternatives your team is seriously considering, including staying with the incumbent, switching vendors, or building internally.
- Share the single condition about your current approach that would have to be true for you to remain with it instead of changing.
- Rank these possibilities by likelihood, stay with incumbent; move to a commercial platform; develop in-house; hybrid model.
- Indicate whether any internal groups have proposed an in-house solution and who would lead it.
- Give an example of a competitor capability or internal plan that, if matched, would cause you to pause vendor selection.
- Would an incumbent offer of an extended 12-month reagent pricing guarantee be sufficient to keep you from switching?
Can your lab support a new platform on day one?
- Confirm whether your lab could provide dedicated space and a 20A circuit for the instrument within 8 weeks.
- Enumerate the IT and LIS interfaces required for result transmission and who owns each connection.
- Assess whether your network allows outbound secure messaging from instruments, and whether a test endpoint is available for integration testing.
- Indicate whether biosafety approvals, institutional review, or other compliance steps are needed before clinical use.
- State the headcount you can commit to training and go-live support, by role and percent FTE during the first 90 days.
- Choose whether a required lab upgrade that pushed deployment beyond your target window would stop the project or only shift the timeline.
Decision drivers and financial thresholds
- Identify the financial metric you will use to judge a platform investment: total cost per test, 3-year ROI, cost per avoided hospital day, or a different KPI.
- Estimate your target total cost per test that would justify replacing current workflows.
- Confirm whether reagent supply agreements or capital approval are already budgeted for this fiscal year.
- Select the procurement hurdles that would delay or block a contract, capital committee approval, contract review, procurement vetting, or supply chain concerns.
- Can you commit to a letter of intent within 30 days if a pilot meets your performance targets?
- Name the decision-makers by title who must approve purchase and their primary concern category, clinical, operational, financial, or IT.
Next steps and pilot success signals
- Assuming the pilot meets acceptance criteria, what would accelerate full rollout to a signed contract?
- Choose the top three measurable success signals you will track during pilot, TAT reduction, sensitivity, hands-on time, operator error rate, reagent cost per test, LIS integration time.
- Select how often you want schedule checkpoints during pilot, weekly, biweekly, or monthly.
- Outline the escalation path and SLA expectations for critical tickets during pilot and first 90 days.
- Decide whether a pilot that fails to meet more than one primary acceptance criterion would require a re-run, a root cause analysis with named owners, or termination of the project.
- By when do you expect a procurement decision if pilot signals match targets, immediately after pilot, within 30 days, within 90 days, or longer?
-
Clinical Workflow Experience
Map how the platform delivers targeted outcomes in the buyer's real scenarios — sample intake, turnaround time expectations, reporting, and downstream clinical impact.
Solution Experience
- Clinical Workflow Experience Session
- Confirm the current state and its cost
- You confirm the demonstrated workflow delivers results within your target turnaround time and removes the delays you described.
- Provide four weeks of specimen volumes by specimen type and target turnaround times for modeled runs.
- Walk a real sample pathway end to end
- You confirm the operator tasks and staffing model shown will fit your available staff without requiring unacceptable additional FTEs or space.
- Run a site-specific sample forecast and deliver a modeled throughput, reagent burn-rate, and operator task map before the follow-up session.
- Prove turnaround and reporting in your scenario
- Share your LIS message format requirements and any existing integration constraints for a connectivity feasibility check.
- You agree on the validation evidence and acceptance criteria that will be required before go live.
- Draft proposed validation acceptance criteria based on the demonstrated runs for joint review at the next meeting.
- Review validation and acceptance criteria
- Validate alignment explicitly
- Agree next steps and commitments
- Clinical Workflow Experience Session
- Clinical Workflow Experience Deck
- Clinical Workflow Solution Brief
- meeting
- slides
- document
-
Solution Scope
Define instrument model, assay menu, throughput, consumables supply, validation plan, training, LIS connectivity, responsibilities, and acceptance criteria.
Scope Configuration
- Deliver and install instrument
- Perform IQ/OQ/PQ qualification
- Provide assay validation kits and protocols
- Deploy syndromic multiplex panels
- Deploy antimicrobial-resistance detection panels
- Configure and test LIS (HL7) interface
- Train laboratory operators and competency certification
- Supply reagents and consumables under contract
- Provide preventive maintenance and onsite repair
- Install and validate high-throughput automation module
- Support parallel-run verification and go-live assistance
- Provide instrument financing and lease agreement
Scope Questions
Deliver and install instrument
- What instrument model will you accept for delivery (include model number and any pre-installed options)?
- How much clear bench footprint (cm) and door width will you provide at the planned install location?
- Which facility access requirements apply at your site on delivery day (e.g., loading dock hours, PPE, credentialing)?
- Do you require on-site heavy rigging or soft-floor protection during installation?
- Who will be your on-site contact for delivery and sign-off (name and phone)?
Perform IQ/OQ/PQ qualification
- When do you expect formal IQ/OQ/PQ to occur relative to delivery (select intended window)?
- Where will your IQ/OQ/PQ documentation be stored (LIS, laboratory QMS, or paper file)?
- List the regulatory standards your qualification must reference (e.g., CLIA, CAP, ISO 15189).
- Provide the acceptance criteria you require for operational qualification runs (e.g., percent concordance, limit of detection, control performance).
- Estimate how many IQ/OQ/PQ run replicates you require per assay or instrument channel.
Provide assay validation kits and protocols
- Confirm which assay panels you will validate first (list panel names or targeted pathogens).
- Specify the lot numbers and expiration windows you need included with each validation kit.
- Are there required comparator methods for your validation (e.g., culture, reference PCR, sequencing)?
- Select the sample types you will use for validation (e.g., nasopharyngeal swab, sputum, whole blood).
- Identify any local regulatory submissions you must file to accept validation data (e.g., IRB notification, local health authority).
Deploy syndromic multiplex panels
- Describe the clinical use cases you expect for the syndromic panels (e.g., respiratory triage, neonatal sepsis, ED admission screening).
- Indicate the target turnaround time you require from sample accession to report for each panel (hours).
- Assign projected daily throughput for each syndromic panel (tests per 8-hour shift).
- Name the control materials and external quality assessment (EQA) programs you will run for these panels.
- Attach any institutional testing algorithm or formulary that dictates when the syndromic panel is ordered.
Deploy antimicrobial-resistance detection panels
- State which resistance markers (genes or mutations) must be covered by your AMR panels (e.g., mecA, blaKPC, NDM).
- Measure the acceptable positive predictive value or concordance threshold you require for resistance calls (%).
- Report how you will route AMR results into your antimicrobial stewardship workflows (e.g., automatic alert to ID physician, pharmacy notification).
- Clarify which specimen types will carry AMR testing at your site (e.g., blood culture, wound swab, respiratory aspirate).
- Outline the turnaround time requirement for AMR panel results to impact therapy decisions (hours).
Configure and test LIS (HL7) interface
- Choose the HL7 message types you need supported at go-live (e.g., ORM^O01 for orders, ORU^R01 for results).
- Enter the primary receiving IP/port and expected secure transport method for your LIS connection (MLLP, VPN, TLS).
- Supply the LOINC and SNOMED codes you require for structured results reporting or indicate if you want us to map them.
- Record the patient and specimen accessioning fields from your LIS that must be preserved (e.g., medical record number, accession number, specimen ID).
- Set the test result turnaround time (TAT) SLA you expect for reported HL7 messages.
Train laboratory operators and competency certification
- What operator roles at your laboratory require training and competency certification (e.g., technologist, supervisor)?
- How many operators need initial training and how many will require annual competency refreshers at your site?
- Which competency assessment format do you prefer for operators (observed run, written test, proficiency panel)?
- Do you require operator competency certificates to be issued and tracked in your learning management or training system?
- Who at your organization will be authorized to sign operator competency acceptance for go-live?
Supply reagents and consumables under contract
- When do you expect the first reagent shipment relative to installation (choose timing)?
- Where should routine reagent and consumable shipments be delivered for your site (central receiving, lab door, off-site warehouse)?
- List the reagent SKUs and your forecasted monthly usage per SKU.
- Provide the desired contract term and any minimum annual purchase commitment you require.
- Estimate required on-shelf stability or cold-chain constraints for your consumables (e.g., -20°C, 2-8°C).
Provide preventive maintenance and onsite repair
- Confirm your preferred preventive maintenance frequency for the instrument (monthly, quarterly, semi-annual).
- Specify the maximum acceptable mean time to repair (hours) for critical failures at your site.
- Are you subject to uptime or availability requirements that mandate scheduled maintenance windows?
- Select the spare-part coverage you desire under contract for your instrument.
- Identify any on-site safety or lockout/tagout (LOTO) procedures your technicians must follow.
Install and validate high-throughput automation module
- Describe the automation module capacity you need and how it should integrate with your upstream sample preparation (samples per hour).
- Indicate the space and service requirements you must provide for the automation module (power amps, compressed air, floor loading).
- Assign the barcode and sample plate formats the automation must accept at your lab (e.g., 96-well, 384-well, 15 mL tube).
- Name the throughput acceptance criteria you require for the automation (minimum tests per shift and acceptable sample rejection rate).
- Attach any validated SOPs or robotics safety assessments your site requires prior to start-up.
Support parallel-run verification and go-live assistance
- State the duration of the parallel run you require before switching routine reporting to the new system (days).
- Measure the concordance threshold you require between the new system and the comparator method for go-live (%).
- Report who at your organization will own discrepancy review during parallel runs and how you will provide rapid feedback.
- Clarify which patient cohorts or specimen types must be included in your parallel verification.
- Outline the escalation steps you want if parallel-run concordance falls below the agreed threshold.
Provide instrument financing and lease agreement
- Choose the financing structure you prefer for procurement of the instrument.
- Enter the desired lease term and any end-of-term options you require (purchase, return, renewal).
- Supply the internal approvals or credit documentation your finance group requires for financing.
- Record any budget or capital-approval deadlines we must meet for your procurement cycle.
- Set your payment cadence preference and billing entity for the agreement.
-
Mutual Commit
Finalize commercial terms, reagent and service commitments, validation acceptance criteria, delivery schedules, and mutual obligations for go‑live.
Agreement Modules
- Purchase Agreement
- Order Confirmation
- Master Services Agreement (MSA)
- Statement of Work (SOW)
- Consumables & Reagent Supply Agreement
- Validation Acceptance Protocol
- Delivery & Go‑Live Schedule
- Service Level Agreement (SLA)
- Payment Schedule & Commercial Terms
- Acceptance Certificate
- HIPAA Business Associate Addendum (conditional)
-
Deployment
Operationalize instrument installation, integrations, and lab validation with readiness checks and coordinated execution.
-
Pre-Deployment Readiness
Capture concrete readiness facts the deployment depends on — lab footprint, power/ventilation, biosafety, IT/LIS access, staff availability, and regulatory approvals.
Pre-Deployment Questions
Environment and site access
- Is the installation room/site confirmed and accessible for delivery and installation? (This lets us schedule delivery and field service.)
- Are the physical/environmental prerequisites confirmed: electrical/power circuit, HVAC/ventilation, bench/floor footprint, and biosafety level? (If anything is outstanding, we'll need owners and dates.)
Data and integration
- Is the laboratory information system (LIS) or middleware integration endpoint and owner identified and authorized for instrument connection? (We need an owner to request interface details.)
- Has IT/network approved instrument network access and firewall/port exceptions required for connectivity? (So we can coordinate remote support and LIS integration.)
People and ownership
- Who is the buyer's named on‑site deployment owner responsible for coordination, access approvals, and final acceptance? (Provide full name, role, and best contact.)
- Are the primary operators and validation leads identified and available for initial training and onsite validation runs? (We need names and shift coverage during go‑live.)
Timing and constraints
- Are there scheduled blackout windows, high‑volume periods, or dates when installation/validation cannot occur? (So we can avoid clinical disruption.)
- Are any regulatory or institutional approvals required before installation (biosafety committee, procurement sign‑off, compliance review), and what is their status?
-
Configuration Details
Lock exact configuration values the deployment team will use — instrument serials, network settings, LIS message formats, user roles, and SOP/run parameters.
Configuration Details
Anchoring the Production Environment
- Enter the canonical deployment environment name that will be used in all configuration (format: production / staging / qa). Default: production.
- Enter the platform instance base URL the deployment will configure (format: https://subdomain.example.org).
- Select the geographic region where the primary instrument will operate (this drives support routing and documentation variants). Default: North America.
- Enter the platform software release or version string the deployment should install (example: 2.4.1-build-2025).
- Is this a buyer-managed network environment or seller-hosted environment? Default: Buyer-managed.
Pinpointing the Instrument(s)
- Enter the primary instrument model to configure (select the exact model name as it appears on the spec sheet).
- Enter the primary instrument serial number that will be used for production (format: SN-XXXX-XXXX).
- Will a secondary (backup) instrument be installed at the same site? Default: No.
- If Yes to backup instrument, enter the backup instrument serial number (single value; leave blank if none).
- Enter the on-site location identifier where the instrument will sit (format: Building-Room or Laboratory name — this is the exact label used for shipping and asset tagging).
- Enter the declared power circuit requirement for the instrument (amps). Default: 20.
Network & Connectivity Settings
- Preferred network addressing method for the instrument (Default: DHCP).
- If Static IPv4 selected, enter the instrument IPv4 address (format: 192.0.2.10). Leave blank if DHCP.
- If Static IPv4 selected, enter the subnet mask (format: 255.255.255.0). Leave blank if DHCP.
- If Static IPv4 selected, enter the default gateway (format: 192.0.2.1). Leave blank if DHCP.
- Enter the instrument hostname to register in DNS (example: mol-dx-lab1).
- Does the instrument require outbound TLS access to the seller's update and telemetry endpoints? Default: Yes.
- If outbound TLS required, enter the proxy FQDN or 'DIRECT' if not required (format: proxy.corp.local or DIRECT).
LIS / Result Reporting Configuration
- Select the message format the LIS will accept (choose the single primary format).
- Select the transport mechanism for sending results to the LIS (Default: HL7 over MLLP where supported).
- Enter the target LIS system name as the buyer refers to it (exact string used in configuration).
- Enter the LIS receiving endpoint hostname or IP (format: host.example.org or 192.0.2.20).
- Enter the LIS receiver port (numeric). Default for MLLP: 2575.
- Enter the sending facility code that should appear in outbound messages (HL7 MSH-4 / FHIR source identifier).
- Who will own the credential exchange for the LIS integration (select one — the secret itself will be exchanged via your secure channel at kickoff).
- If the message format is Custom or Other, enter the single-file location or schema name to be used (example: custom_oru_v2_schema_v1).
User Roles, Accounts, and Access
- Select the standard system roles to create for the site (select all that apply).
- If you selected Other role(s), enter one exact role name to create (single value).
- Enter the primary lab admin account username (non-secret identifier; will be provisioned as the account owner).
- Enter the primary lab admin email address (format: [email protected]).
- Number of operator accounts to pre-provision (numeric). Default: 3.
- Will the buyer use an identity provider (IdP) for SSO? Default: No.
- If using an IdP, enter the IdP entity ID or client ID (non-secret identifier). Do not paste secrets here.
Assay, Run Profiles, and SOP Parameters
- Enter the default assay/run protocol name to be set on the instrument (exact string from your SOP).
- Enter the default number of samples per run for the standard workflow (numeric). Default: 24.
- Enter the default run timeout in minutes (numeric). Default: 90.
- Select the default result reporting granularity (Default: Full quantitative + qualitative).
- Should the system append interpretive comments to results by default? Default: No.
- Enter the name of the local SOP document version that this configuration matches (exact string).
Consumables, Reagents, and Initial Supply Pack
- Enter the consumable SKU that should be shipped with the initial deployment (single SKU string).
- Enter the initial reagent kit lot number to register on the instrument (single value; do not include expiry date here).
- Initial quantity of reagent kits to ship (numeric). Default: 4.
- Default reorder threshold (number of kits remaining that should trigger a replenishment order). Default: 2.
- Preferred replenishment cadence (Default: Monthly).
Validation, Acceptance Criteria, and Go/No‑Go
- Enter the required number of positive control runs for site analytical validation (numeric). Default: 3.
- Enter the required number of negative control runs for site analytical validation (numeric). Default: 3.
- Specify the minimum positive agreement (PPA) threshold (%) for acceptance. Default: 95.
- Specify the minimum negative agreement (NPA) threshold (%) for acceptance. Default: 98.
- Enter the single acceptance authority name who will sign validation acceptance (exact role or person).
- Enter the planned date for completion of onsite validation (format: YYYY-MM-DD).
Delivery, Installation, and Onsite Logistics
- Preferred delivery date for the instrument (format: YYYY-MM-DD).
- Preferred installation start time window (Default: 09:00-17:00 local).
- Enter the onsite contact name for delivery and install (single person; exact name).
- Enter the onsite contact phone (format: +CountryCode-Number).
- Will the site provide a forklift or mechanical lift for instrument delivery? Default: No.
- Does the installation location require special building access instructions (single short string such as gate code or 'Escort required')? Enter that instruction or 'None'.
Support Path, Escalation, and Ticketing
- Select the primary support channel to open operational tickets (Default: Seller support portal).
- If Buyer IT ticketing system selected, enter the ticket queue name to use (single string).
- Enter the primary on-call support contact name for escalation (single name).
- Enter the primary on-call support contact email (format: [email protected]).
-
Deployment
Coordinate delivery, installation, connectivity, onsite validation runs, operator training, and go‑live sequencing with named owners and milestones.
-
-
Success
Monitor clinical and operational outcomes against success criteria, capture lessons learned, and maintain a shared channel for issues, support tickets, and enhancement requests.
Success Reviews
- Go‑live Health Check (weeks 1–4)
- First Measurement Review (weeks 4–10)
- Acceptance Gate Meeting (around day 90)
- Ongoing Quarterly Success Review
Issues & Enhancements
- Schedule operator refresher training for identified competency gaps and confirm dates.
- Publish an operator retraining plan and updated SOPs addressing identified gaps.
- Resolve or escalate high‑impact support tickets affecting test run failure rate before the Acceptance Gate.
- Restate acceptance criteria and numeric targets
- Produce a documented acceptance decision with a named signatory for the buying organization.
- For any failed criteria, agree a remediation plan with deadlines and evidence requirements.
- Confirm the status of incumbent decommissioning and data migration to avoid dual‑system fallbacks.
- Publish the formal acceptance record with the named signatory and archive it in the shared workspace.
- List remediation tasks for unmet criteria with deadlines and evidence deliverables.
- Complete incumbent system decommissioning steps or publish the retention and read‑only plan and archive confirmation.
- Operational metrics review
- Confirm the system continues to meet the key operational targets or document a remediation trajectory.
- Reduce the count of high‑priority open support tickets and agree closure dates.
- Prioritize enhancement requests for the next quarter with acceptance criteria and delivery windows.
- Publish the quarterly metrics report showing trends against Solution Scope targets.
- Update the enhancement backlog with priorities, acceptance criteria, and planned delivery quarters.
- Reconfirm success criteria and ownership
- All deployment validation checkpoints are confirmed or have scheduled remediation.
- Active issues are logged with remediation actions and target dates.
- Date for the First Measurement meeting is confirmed.
- Publish the deployment validation checklist with status and remediation dates.
- Update the shared issue log with prioritization and expected resolution dates.
- Confirm data sources and owners for the metrics to be presented at the First Measurement meeting.
- Agree a prioritized set of corrective actions with resolution dates and evidence required for acceptance.
- Present first outcome data against targets
- Determine whether each named metric is trending toward the Solution Scope target and document reasons for any shortfalls.
- Confirm the acceptance gate date and required deliverables for the Acceptance Gate meeting.
- Run targeted root cause analyses for the top two underperforming metrics and deliver a diagnosis document.
- Present outcome data for each acceptance criterion
- Persistent issue burn‑down and ticket review
- Root cause diagnosis for gaps
- Deployment and migration validation
- Document pass or fail per criterion and capture signatory
- Operator proficiency and training review
- Enhancement and improvement backlog review
- Early adoption signals and usage patterns
- Support tickets and remediation plan
- Open issues and blockers
- Agree remediation plan for any unmet criteria
- Training and staffing forecast
- Confirm path and timeline to the Acceptance Gate
- Immediate remediation actions and next steps
- Incumbent system decommissioning and data migration status
- Agree next quarter actions and short checklists