ComplianceLive · in the productQueue & board

Security Centre

The security answers a hospital’s IT committee files — and its DPIAs, processors, patches, vendor sessions and leavers on one register.

Installs with MakerChecker, whose screen it works on

Get Security Centre Open the appAvailable nowHow pricing works →

What it is

One screen that answers the questionnaire: who signed in and whether they used a second factor, which devices are live and how to end one, the quarterly review of every grant carrying the whole patient record or the money, and a printable statement for a patient of exactly who opened their file and why — with emergency accesses called out. Underneath it, the statutory privacy desk: access, correction, erasure, nomination, consent withdrawal and objection, each on a thirty-day clock with a named grievance officer. Its IT registers keep the rest of the committee’s file: a Data Protection Impact Assessment for each new feature or new use of personal data, signed off by the officer the privacy office names and frozen once signed; the hospital’s own processors with what each receives, where it is stored and when its agreement is due for review; every computer’s operating system and antivirus against the latest version the practice recorded; every AMC vendor’s remote session from access granted to access revoked, with an overstaying one first; and a leaver’s shut-off checklist for every system they had a login to, copied from the practice’s own list when HireDesk records the exit.

Who uses it: Built for: Every specialty
Reads: Sign-ins, the audit chain, role grants, the vault, job runs, exit cases
Writes: Access reviews, privacy requests, retention rules and sweep logs, DPIAs and DPO sign-offs, processor register, patch status, vendor remote sessions, leaver shut-off checklists
Never: It asserts nothing.
Access: Only people whose role includes it — the clinic owner decides who
Your data: Full PHI. Hosted in Boston, United States. On uninstall: Reviews, privacy requests and sweep logs stay with the tenant as evidence.

In the product

Who uses it: Quality officer — the demo profile it is best tried as
Where it opens: Compliance › Security Centre /security
Permission: security.read

Every compliance app in the handbook →

How it works

Name the grievance officerOne person, reachable, whose name is printed on every privacy notice the clinic hands out.
Open the quarterly access reviewEvery grant carrying the whole patient record, the money, the platform console or emergency access is listed for a manager to attest or challenge. A challenge needs a second person to approve before anything is removed. Leavers, vendor sessions and patches sit beside it on the IT registers.
Work the privacy queueLog the request the day it arrives, record how you checked identity, then answer it in writing inside thirty days.
File the summaryPrint the posture summary. It carries this morning’s numbers and only the claims those numbers support — and the DPIAs the officer signed off are on the register beside it.

Rules it keeps

What it does not do, by design. A listing with only benefits is an advertisement.

It asserts nothing.

Every figure is measured from a row somebody else wrote, and a figure it could not read says “not known” rather than “OK”.

It does not install a patch, grant a vendor’s access or disable a login in another system — IT does that; the registers record that it was done.

No latest version or patch interval ships: the practice records each with its source.

Erasure replaces identifiers and keeps the clinical record under the retention the clinic has stated; a legal hold stops it outright and produces the written refusal the person is owed.

No statutory period is shipped: the clinic states the period and cites its source, and the patient’s notice quotes that citation back.

AI in Security Centre

AskQuestions about what is on screen — “What needs attention in Security Centre today?” — answered with the records it read.

DraftSummaries and notes for the team, marked as drafts until a person signs.

Every answer shows its sources. Nothing AI writes is saved until a person accepts it.

See it on screen

Security Centre — Security Centre — See who signed in, review privileged access, answer privacy requests — 01Security Centre — See who signed in, review privileged access, answer privacy requestsCaptured from the running demo clinic

01Security Centre — See who signed in, review privileged access, answer privacy requestsCaptured from the running demo clinic

1 of 1

Connected to

Read out of the code, not the brochure: each app below is here because one service queries the other’s tables. Install either side and the hand-over is already wired.

Reads from · 7

BillDesk CaseNotes Hiring MakerChecker Patient Registry RetentionVault ReviewMagnet

Hands to · 4

GDPRDesk HIPAAGuard MakerChecker Patient Registry

See the whole clinic →

Questions clinics ask

What does Security Centre do?

The security answers a hospital’s IT committee files — and its DPIAs, processors, patches, vendor sessions and leavers on one register. One screen that answers the questionnaire: who signed in and whether they used a second factor, which devices are live and how to end one, the quarterly review of every grant carrying the whole patient record or the money, and a printable statement for a patient of exactly who opened their file and why — with emergency accesses called out. Underneath it, the statutory privacy desk: access, correction, erasure, nomination, consent withdrawal and objection, each on a thirty-day clock with a named grievance officer. Its IT registers keep the rest of the committee’s file: a Data Protection Impact Assessment for each new feature or new use of personal data, signed off by the officer the privacy office names and frozen once signed; the hospital’s own processors with what each receives, where it is stored and when its agreement is due for review; every computer’s operating system and antivirus against the latest version the practice recorded; every AMC vendor’s remote session from access granted to access revoked, with an overstaying one first; and a leaver’s shut-off checklist for every system they had a login to, copied from the practice’s own list when HireDesk records the exit.

What data does Security Centre read and write?

Security Centre reads sign-ins, the audit chain, role grants, the vault, job runs, exit cases and writes access reviews, privacy requests, retention rules and sweep logs, DPIAs and DPO sign-offs, processor register, patch status, vendor remote sessions, leaver shut-off checklists. Its data class is Full PHI. Every app works on the same patient record — nothing is copied into a silo.

What does Security Centre deliberately not do?

It asserts nothing. Every figure is measured from a row somebody else wrote, and a figure it could not read says “not known” rather than “OK”. It does not install a patch, grant a vendor’s access or disable a login in another system — IT does that; the registers record that it was done. No latest version or patch interval ships: the practice records each with its source. Erasure replaces identifiers and keeps the clinical record under the retention the clinic has stated; a legal hold stops it outright and produces the written refusal the person is owed. No statutory period is shipped: the clinic states the period and cites its source, and the patient’s notice quotes that citation back.

What happens to our data if we uninstall Security Centre?

Reviews, privacy requests and sweep logs stay with the tenant as evidence.

Is Security Centre available today?

Yes — Security Centre is live in clinics today. Set up your practice on MedAppz and install it from your dashboard.

Want to see Security Centre running on your own patients?

Tell us what you run and we will show you this app inside a practice shaped like yours — or answer the question the page above did not.

More in Compliance

All 89 →