Private evaluation · customer-controlled environment

Protect the document. Keep control of the data.

Medshield runs inside the customer's VPC or on-premise environment. It produces protected files, quarantine decisions, and evidence your engineering and security teams can inspect.

Evaluation-stage software. Medshield is not clinically validated and does not establish HIPAA compliance or a Safe Harbor determination. Never send PHI through this website, email, or the pilot application.

6–8 weeksfixed-scope private pilot
Two stagessynthetic, then customer-controlled validation
Two deployment modeson-premise or customer VPC
Zero hosted uploadsno Medshield PHI collection

Designed for a specific workflow

For healthcare AI and clinical-data vendors that ingest documents.

Use Medshield as a controlled preprocessing and evidence layer before clinical PDFs, scans, office files, and structured documents reach analytics, abstraction, research, or AI systems.

01

Clinical AI

Reduce identifier exposure before documents enter model and retrieval pipelines.

02

Data platforms

Produce protected artifacts, audit output, and explicit quarantine decisions.

03

Abstraction teams

Combine machine first pass with human risk review and expected-answer fixtures.

04

Research workflows

Evaluate document-specific behavior without sending source records to a hosted service.

Deployment boundary

Your environment remains the data boundary.

Customer environmentClinical documentsVPC or on-premise
Single-tenant processingMedshieldLocal OCR, detection, redaction, quarantine
Customer-controlled outputsProtected artifactsAudit manifest and review queue

Self-managed: your team operates the deployment using the agreed evaluation package.

Medshield-managed: Medshield operates a single-tenant deployment inside your cloud account under approved, logged access.

Out of scope: vendor-hosted PHI processing and multi-tenant uploads.

Synthetic evidence

Review what one run proves—and what it cannot.

Every public receipt uses invented data. Customer-specific performance is measured only against an agreed fixture set and expected-answer file.

Current viewer
Current Medshield viewer showing a synthetic before-and-after document comparison

Artifact-level review

Inspect the original, protected result, processing stages, policy lane, and detected-identifier evidence together.

Proof of current product behavior on one fixture.
File-level proof
Animated terminal proof comparing live PDF text and bytes before and after protection

Covered is not removed

Protected PDFs are flattened and checked for extractable text and known literal bytes—not merely drawn over.

Proof of removal for known synthetic values.
Known boundary
Medshield evidence boundary separating demonstrated behavior from unproven claims

Detection is the hard part

The current shorthand probe detects 10 of 13 expected identifiers. Misses remain evaluation inputs, not hidden footnotes.

Not evidence of universal recall or compliance.

Operating boundary

Human review and quarantine remain part of the design.

Known gaps: handwriting, full-face photographs, signatures, DICOM, and some high-entropy identifiers.

Packaging: handling unredacted originals is an operational control outside the detector.

Validation: production recommendations require customer-specific thresholds and documented review.

Claims: no certification, universal recall, breach prevention, or freedom from human review.

Private paid pilot

A decision process, not an open-ended proof of concept.

Pricing is shared after qualification. The pilot has a fixed scope, written acceptance criteria, and a final proceed/remediate/stop recommendation.

  1. Week 0

    Contract and boundary

    Security review, architecture, SOW, data rules, and acceptance criteria.

  2. Weeks 1–2

    Deploy

    Install inside the customer VPC or on-premise environment.

  3. Weeks 2–4

    Synthetic evaluation

    Run representative document shapes with expected answers.

  4. Weeks 4–7

    Controlled validation

    Optional customer-controlled PHI stage only after the required approvals.

  5. Week 8

    Decision report

    Metrics, failures, remediation plan, and production-readiness boundary.

Security posture

No customer documents through this website. No vendor-hosted PHI service.

  • Private proprietary source repository
  • Customer-controlled deployment and outputs
  • Remote support access disabled by default
  • No raw identifiers in standard audit output
  • No uploads, analytics, or browser storage on this site
  • Security and architecture brief available after qualification

For qualified US healthcare vendors

Request a private pilot conversation.

Start with business identity and a broad workflow category. Yash reviews every request and sends the detailed questionnaire, scheduling link, or both when there is a plausible fit.

  • No document or file uploads
  • No patient, clinical, or production information
  • Founder review within one business day
Request a conversation

Business information only

Tell me where Medshield may fit.

Required fields are marked. This form must never contain PHI, patient details, screenshots, filenames, clinical records, or production logs.