Security and data handling

Both products run on Amazon Web Services (AWS), in a United States region. Techinquest runs the application and the AWS environment it sits in, and applies the updates. Your teams use it in a web browser.

Each customer is deployed separately. Your organization gets its own application deployment and its own database, not a share of one that other customers use.

The application reaches its database through a login that can read and write records but cannot change the structure of the database. Databases are backed up automatically every day, and the backups are encrypted like the database itself.

Access to the production environment is restricted to authorized Techinquest administrators. Employees and contractors sign confidentiality agreements.

In transit

Browsers reach both products over HTTPS, with TLS 1.2 as the minimum version, and plain HTTP requests are redirected to HTTPS. Scheduled file transfers run over SFTP, which encrypts the connection.

At rest

Databases, database backups and stored files are encrypted with AES-256, using keys managed by AWS. Database keys are held in the AWS Key Management Service.

The security pack sets out the configuration behind each of these statements.

Your staff sign in with their existing organization account, through single sign-on. The products use a managed AWS sign-in service that hands authentication to your identity provider. Your password rules and multi-factor requirements apply, and a person disabled in your directory can no longer sign in.

People outside your organization, such as vendor reps and supplier contacts, each get an individual account. In Implant Control, your administrators create these accounts, set what each one can see, and deactivate them. Multi-factor authentication is available for these accounts but is not yet required for every one of them. We will show your reviewers exactly how it is set up for your deployment.

Access is role-based in both products. A role decides which screens and actions a person has, and a user can be limited to particular hospitals.

Implant Control

Vendor reps and vendor managers see only requests for the vendors and hospitals their account is assigned to. Which request lines can be added, changed or deleted at each status comes from one permission table. It is enforced on the server, not only hidden in the screen, and covered by automated tests.

Rebate Recovery

Six health-system roles, plus supplier roles. Supplier users see a dashboard limited to their own contracts, and that limit is applied on the server. Users can be restricted to particular hospitals or suppliers. New screens open to administrators first and reach other roles later.

Both products work on files, so there is no interface to build into your ERP or EMR and no API to open on them.

Implant Control

Surgical case and schedule exports from your EMR arrive on a schedule. Approved requests leave as a requisition file for your ERP, and purchase order numbers come back in a return file.

Rebate Recovery

Contract and purchasing data arrives as CSV or Excel files, uploaded in the browser or delivered for scheduled processing. Each upload is checked before anything loads, and rejected rows are reported back.

Scheduled transfers use SFTP. Your systems connect out to a Techinquest transfer endpoint to deliver and collect files, so nothing inside your network has to accept a connection from us.

Implant Control also emails vendor reps about their own requests, for example with the purchase order number when a request completes.

Implant Control

Requests, lines, notes, contracts, prices, users and vendors all keep a change history. An audit trail screen shows each insert, update and delete with who made it, when, and the values before and after. Each validation run is stored with the case lines it matched, and a purchase order number keyed by hand carries the same trail as one loaded from a file.

Rebate Recovery

Contract and purchasing records carry who created them and who last changed them, and when. Each data file load is logged with its outcome and the rows it rejected. Each AI exchange is logged with who made it, what was asked, the answer and when.

One thing to plan around: Rebate Recovery recalculates rebate figures from current data rather than keeping a point-in-time history of every figure. An export taken at period close is the snapshot to file.

AI appears only in Rebate Recovery. Implant Control has no AI features.

Model requests go to Amazon Bedrock, the managed AI service inside AWS, using its United States routing. The cross-Region inference documentation explains that this routing processes each request in a Region within that geography. The Bedrock data protection documentation states that model providers do not have access to customer prompts and completions.

Reading a contract

A person uploads a signed supplier agreement and the model proposes a draft contract from it. The agreement itself goes to the model, because reading it is the job. Each extracted value shows whether its wording was found on a cited page. A rate or amount with no quote behind it blocks creation until a person confirms they checked it, and the result is always an inactive draft.

Answering questions

The assistant is read-only. It cannot change a contract, link a payment or dismiss an alert. It answers from the same reports the person asking is allowed to run, and it is built to take every figure from those reports rather than from the model. Supplier and contract names on file are replaced with stand-ins before a request leaves the system, and restored in the answer.

Logging

Each exchange is logged with who made it, what was asked or read, the full answer and when. An assistant answer that contains a figure the system could not trace to a report is flagged in the log.

Alerts, calculations and dashboards are rules and arithmetic. None of them is AI.

This page is a summary. For a formal review we provide:

The security documentation pack

An architecture and data-flow description, encryption detail and our answers to a standard vendor security questionnaire, shared under NDA. Each answer is marked as in place, partly in place or planned, and planned work is never presented as done.

Answers to your questionnaire

We complete your organization's own vendor security questionnaire and walk your reviewers through our controls, with the people who build and run the products.

To report a suspected security issue in either product, email support@tech-inquest.com.