Skip to the content
Novixo

Security and validation

Controls you can inspect, and a plain account of what remains yours

Safety data is patient data, and a safety system has to stand up to an inspection. This page describes the controls built into IntakeX Cloud, how its AI is governed, and what a validation of it involves.

Each customer isolated twice

The workspace of a request comes only from the verified sign-in, never from the request itself. Underneath, the cloud provider’s access control allows a workspace’s credentials to reach that workspace’s records and files and nothing else. A defect in the application ends in a refusal.

Encryption and keys

Data is encrypted in transit and at rest, with keys held in a managed key service. Credentials for receiving systems are kept in a secrets store, never in the case data or the configuration.

Identity and roles

Every account signs in with a password and an authenticator code. Roles separate the administrator, the case processor, the medical reviewer, the submission manager and the read-only auditor. Sessions end after fifteen minutes without input.

A tamper-evident audit trail

Every change to a case, a user or a setting is written to an append-only, hash-chained trail in the same transaction as the change. Each day the heads of the chains are signed and stored where they cannot be altered or deleted.

Versions that cannot be rewritten

A case’s content is immutable per version, stored with its hash and read back only if it still matches. A change is a new version with its author, time and, for a person’s change, a reason.

Electronic signatures

Approval and rejection in medical review require the password and a current authenticator code. The signature records the signer, the meaning, the time, the version and its hash. A later change shows the signature as superseded.

How the AI is kept honest

A language model can read a faxed form better than any rule set. It can also be wrong with complete confidence. The product is designed around the second fact as much as the first.

  • The model reads and proposes. Values are validated, quoted passages are checked against the document, codes are read from the dictionaries.
  • The model in use is pinned, and every instruction given to it is versioned. Both are recorded with each call.
  • An evaluation set with known answers is run after every change to an instruction or to the model.
  • A value that cannot be confirmed in the source, or a sentence nothing supports, stops the case for a person.
  • Each workspace decides which steps may use a model at all.

Validation

The documents a validation needs, already written

No software is compliant by itself. A computerised system is validated by the company that uses it, for the use it intends. What a supplier can do is build the controls in and hand over documentation that is specific, testable and candid.

  • Validation plan
  • User requirements
  • Functional specification
  • Risk assessment
  • Traceability matrix
  • IQ, OQ and PQ protocols
  • 21 CFR Part 11 and EU Annex 11 assessment
  • HIPAA Security Rule mapping
  • Data integrity (ALCOA+) assessment
  • AI governance
  • Runbook, administrator and user guides
  • A register of known limitations

What remains with you

We would rather say this here than have you find it in an audit.

  • Validating your configured instance for your intended use, and signing the protocols
  • The agreements with your cloud provider, including any business associate addendum
  • Your licences for MedDRA and WHODrug, and loading each new release
  • Who gets which role, and your own procedures for review and release
  • Testing the connection to your safety database and to regulators’ gateways

The known-limitations register lists what is not implemented, not yet verified or simplified, with what to do about each. It is part of the pack we share under a confidentiality agreement.

Reporting a security concern

If you believe you have found a weakness in a Novixo product or in this website, write toinfo@novixo.co.in with “Security report” in the subject line. We will acknowledge it and keep you informed.

Send us your security questionnaire

Your quality and security teams will have questions. We answer them in writing, with references to the documents and the tests behind each answer.