For IT and security
What Pare holds, and what it never does.
For an IT or security reviewer: what is held, where, who can reach it, and what the facility has to connect.
- Never heldNo field for a patient.
No patient names, identifiers, dates of birth or diagnoses, and no link between a patient and a procedure. When a schedule export is uploaded, its patient columns are dropped as the file is read.
- FirstA BAA before any data is handled.
Pare signs a Business Associate Agreement with each customer.
- To connectNo EMR project.
Pare runs on a schedule export, a catalog built from your order history and one camera. The record comes out as CSV today; HL7 to your EHR and ERP is next.
- The cameraThe back table only.
Faces and patient labels stay out of frame, and Pare keeps package images, not video of the room.
- Not claimedSOC 2 audit in progress.
Pare displays no compliance seal. A security overview and answers to a security questionnaire are available on request.
How it is built and run.
- Where it runs
- Amazon Web Services in the US West (Oregon) region, on services AWS lists as HIPAA-eligible. The database and the application servers sit in private subnets with no public address.
- Encryption
- Connections use TLS 1.2 or later. The database, stored files, backups, logs and secrets are encrypted with a customer-managed key that rotates every year.
- Sign-in
- Accounts are created by invitation from a facility's own site manager. Sign-in is handled by Amazon Cognito; Pare stores no passwords. Passwords are at least 14 characters, multi-factor authentication is available on every account, and a session ends after 8 hours.
- Access
- Four roles decide what a person can do. Each facility's rows are isolated in the database by row-level security.
- Audit and logs
- Changes are written to an audit log with who made the change, when, and the value before and after. Application, database and network logs are kept for 90 days, encrypted.
- Backups
- Daily, with point-in-time recovery, kept for 14 days, encrypted. Deletion protection is on.
- Package images
- Package images are kept for 90 days, so a disputed charge can be checked against the frame, then deleted. The case record is kept for the life of the agreement. At the end of an agreement, everything is deleted or returned within 30 days, on request.
- Who views images
- An unsure read goes to a trained Pare reviewer, never to a nurse. Reviewers see the package image and the catalog match, nothing else. Access is limited to named Pare staff, logged, and covered by the BAA.
- The camera in the room
- One camera on a ceiling or boom mount over the back table, outside the sterile field. It needs one power outlet and a network connection. The camera does not connect to the EHR or any clinical system.
- Regulatory status
- Pare is not a medical device. It does not diagnose, treat or monitor a patient, has no contact with the patient or the sterile field, and informs no clinical decision. It records supplies for billing and inventory.
- Subprocessors
- Amazon Web Services (hosting), Anthropic (the assistant) and PostHog (usage analytics). A current list is available on request.
For the others in the room
- For supply chainWhat every case used, captured without a nurse typing it.
- For materials managementKnow what every room used, and what's left on the shelf.
- For perioperative leadersCards that match each surgeon, with nothing new for the room.
- For financeWhat can be recovered, and how it is measured.
- For surgeonsYour team changes nothing.
- For your committeePare, in the order a committee asks.
Questions from IT and security?
Fifteen minutes with a founder, or an email. Whichever is easier.
Book a callEmail us