How MORP keeps its records
MORP keeps a complete, automatic history of every case, implant lot, price and invoice. When an auditor, a hospital or a recall asks what happened, your team can answer from the system instead of rebuilding the story from spreadsheets and email. Below is how that works today, and we're happy to walk your quality or IT lead through any of it on a call.
Audit trail
Every time a tracked record is created, changed or removed, MORP records it automatically. Tracked records include cases, implants, lots, prices, contracts, invoices and accounts. Each entry captures who made the change, when, and what the record looked like, so old and new values can be compared field by field. The history is kept by the database itself, so no screen, import or integration can make a change without it being recorded.
Each record's activity feed shows these changes alongside comments, so reviewers can see what changed without leaving the record.
Deleted records
Critical records are never hard-deleted. Removing one sets the time it was removed and the user who removed it, and the record stays in the database and its history.
Regulatory design basis
MORP is designed around the record-keeping requirements of FDA 21 CFR Part 11 (electronic records) and QMSR / ISO 13485:2016, including lot traceability with uniqueness enforced in the database. Compliance tests are tagged to the requirement they cover. MORP is not itself certified or validated by a third party; validating it for your intended use remains part of your quality system, and we support that work.
Access control
Users sign in with email and are assigned roles. Every screen, report and API endpoint checks permissions for the user's role, and the reporting assistant only sees data the user is already allowed to see.
Your own instance
Each customer runs a dedicated copy of MORP with its own database. Your data is not shared with other customers' systems.
API and AI agents
MORP has a documented REST API (OpenAPI) and a remote MCP server that expose the same operations as the screens, authenticated with scoped API keys. You can connect your own tools or AI agents without screen-scraping. The built-in reporting assistant uses Claude with read-only access, scoped to the signed-in user.
Getting your data out
Reports export to Excel and PDF, and all data is available through the API.