NanoSense
Menu
Mode
Read-only
Source
Your existing patient records
Purchase
AWS Marketplace

Answers that cite your own record.

A read-only clinical assistant. Ask a question about a patient, and every statement in the answer links to the chart entry it came from.

Request access Read the data statements
Figure 1 A synthetic question answered from a synthetic record. Hover or focus a citation to see the line it came from.

Clinician asksHow has her HbA1c changed since she started metformin?

Her HbA1c fell from 8.4%1 in January to 7.2%2 in July 2026. Metformin 1000 mg twice daily was started on 3 February3, and no dose change is recorded since.

The record holds no recent creatinine result, so kidney function is not assessed here.

Synthetic demonstration. Not a real patient and not a screenshot of the clinician portal.

1 Lab result, 14 Jan 2026

HbA1c 8.4 % (reference 4.0 to 5.6)

2 Lab result, 9 Jul 2026

HbA1c 7.2 % (reference 4.0 to 5.6)

3 Medication order, 3 Feb 2026

metformin 1000 mg twice daily, started. Status: active.

Abstract

Problem
The answer a clinician needs is usually already in the chart. Finding it means searching several screens.
Method
Ask in plain language. NanoSense reads the patient records already stored in your platform and returns an answer with a citation for each statement.
Boundary
Read-only by design. There is no scheduling, billing, charting or write-back. Your EMR stays the system of record.2
Access
Subscribe through AWS Marketplace. Records come in by EMR CSV import, and sign-in is handled for your clinic.

Statements

Four things we say plainly, because a buyer should not have to infer them.

Data availability
Each clinic’s records are held in an isolated tenant. Row-level security enforces that boundary in the database layer.1
Competing interests
None. NanoSense reads what your platform already holds and cannot change your EMR.2
Compliance
Built for HIPAA. We sign a Business Associate Agreement with every customer. SOC 2 Type II is in progress.1
Audit
HIPAA audit logging, encryption in transit and at rest, and WAF protection are on for every plan.1

Read the full security statements

Methods

Every question follows the same path, and the last step is the one that matters.2

  1. AuthenticateThe request is tied to your tenant and the clinician’s role.
  2. RetrieveRelevant entries are pulled from that tenant’s records only.
  3. ReasonThe assistant drafts an answer from the retrieved entries.
  4. ReturnThe answer arrives with a citation for each statement. Nothing is written back.
Figure 2. The path of one question. Platform details

Case report: Tamartaw

Partner
Tamartaw, a telemedicine platform that connects rural communities in Myanmar with healthcare providers.
Service
NanoSense gives their subscribers AI-powered health summaries, drug interaction checks and deeper clinical analysis as a bundled service.
Data
The deployment runs with de-identified context.
Fallback
The assistant falls back to PubMed when the clinical record has no answer.

Plans and pricing

A flat monthly platform fee plus a per-query rate. No token minimums and no long-term contracts.

Table 1. Plans. Query rates are per query, by mode.
StarterProfessionalEnterprise
Platform fee$19 / month$49 / monthCustom
Fast query$0.015$0.013Custom
RAG+CAG query$0.018$0.015Custom
Deep queryNot included$0.045Custom
Query modesFast, RAG+CAGAll 5All 5
API keys15Unlimited
SupportEmailPriorityPriority
Business Associate AgreementIncludedIncludedIncluded
Every plan includes HIPAA audit logging, encrypted data at rest and WAF protection. Enterprise adds dedicated infrastructure, an on-premises option and a custom SLA.
Request access Compare plans in full

For developers

The same assistant is available as a REST API with tenant API keys, JWT sign-in and a partner service key. JSON in, JSON out.

Read the API documentation

Access

Subscribe through AWS Marketplace. Questions about a BAA or a security review go to hello@nanosense.net.

Request access

References

  1. Security and data handlingControls, retention, subprocessors and shared responsibility
  2. PlatformArchitecture and the path of a question
  3. SolutionsBy type of organization
  4. API documentationEndpoints and authentication
  5. AWS Marketplace onboardingFrom subscription to first query