ClinicOps
Free · browser-local

Map one change before it disappears into seven systems.

Start with one approved or authoritative change, identify the operational surfaces it may touch, assign an owner and capture the evidence state. The mapper builds a portable brief locally in your browser; it does not upload your inputs to ClinicOps.

Use this for scoping and evidence preparation. The mapper does not determine compliance, clinical safety, regulatory acceptability or whether a surface legally must change. Those decisions remain with the appropriately qualified owner.
This utility is a component of the Regulatory Integrity Scanner. Start there for the consolidated single-change and portfolio workflow; this page remains for its focused deep-dive job.

1. Define the change

2. Map affected surfaces

The preset is a starting structure, not a domain conclusion. Mark each surface as affected, not affected, unknown or not assessed; then name the accountable owner and the evidence you expect to close the row.

3. Build the evidence brief

Nothing has been sent or uploaded.

Complete the change and surface map, then choose Build brief.
Use the result to drive the next accountable action. The brief makes affected surfaces, ownership gaps and expected closure evidence explicit so the team can move from a change event to a controlled review.

When the map is real work

If the rows reveal unresolved ownership, missing evidence, cross-system propagation or a large reviewer queue, the paid Regulatory Change Integrity Review turns the defined evidence population into a reviewer-ready reconciliation and closure packet.

Inspect the paid deliverableScope another ClinicOps engagement