Healthcare · Managed platform (PaperCut)

Secure Printing

Patient documents print when the right person is at the printer, with the print system run for you

Book a demonstrationRequest a technical briefingFactsheet

Overview

What you are buying

Moraph resells, implements and runs PaperCut for hospitals and clinics, so print jobs are held until the person who sent them taps their badge at the device. PaperCut keeps a record of what was printed, by whom and where, and Moraph configures release rules, device exceptions and logging with your privacy officer. Moraph monitors the service, manages devices and badge readers, applies approved changes and reviews the service with you every month.

The problem it solves

In a busy hospital, documents with patient information are printed to shared printers in corridors, nurses' stations and clinics, and left in the output tray for anyone to pick up. Staff send jobs to the wrong printer, pages end up with the wrong patient's paperwork, and when a privacy complaint names a printed document there is often no clear record of who printed it or where. Print servers and device settings are maintained by whoever has time, and each site does it differently.

  • Printed patient documents sit unattended in shared output trays
  • Jobs sent to the wrong printer reach the wrong people
  • There is little record of who printed what, where and when
  • Print settings differ from site to site and are rarely reviewed

Who uses it

  • Privacy officers and compliance teams at hospitals, clinics and health systems
  • IT teams who run print servers, devices and desktop support
  • Nursing, registration and clinic leaders whose staff print patient documents
  • Health information management teams
  • Finance and procurement teams who manage print devices and costs

Requirements it supports

HIPAA Privacy Rule safeguards (45 CFR 164.530(c))HIPAA Security Rule (45 CFR Part 164, Subpart C)HIPAA Breach Notification Rule (45 CFR 164.400 to 164.414)Confidentiality of Substance Use Disorder Patient Records (42 CFR Part 2)CMS Conditions of Participation for hospitals: medical record services (42 CFR 482.24)

The product supports these requirements; meeting them remains your organization’s responsibility.

Responsibilities

Who is responsible for what

PaperCut provides the software, Moraph implements and runs it for you, and your organization owns the devices, the network, the users and the privacy decisions.

AreaMoraphPaperCutYour organization
LicensingResells PaperCut licences, or works with licences you already hold, and tracks device counts against themSets the licence terms and the features each edition includesAgrees to PaperCut's terms and decides which edition to license
Platform availabilityMonitors print servers and devices and tells you when an issue affects printingProvides software updates, defect fixes and support to Moraph under its support termsProvides the servers or hosting the agreed deployment needs, unless Moraph hosts them, and keeps a fallback for urgent printing
ConfigurationDesigns the baseline and builds and maintains queues, devices, rules and exceptionsProvides the configuration options the software supportsApproves the baseline and every change to it
Devices and badge readersConfigures devices and readers for PaperCut and coordinates with your device supplierPublishes which devices and readers the software supportsOwns or leases the devices and readers and arranges hardware repair with the supplier
Identity and badgesConnects PaperCut to your directory and badge data and maintains the linkProvides the sign-in and badge options the software supportsOwns the directory and badge system and decides who may print
MonitoringWatches servers, devices and release failures and escalates issues that need a decisionProvides the status information the software recordsDecides on escalated issues
Incident responseRestores printing under the agreed procedure and runs print record searches the privacy officer requestsFixes defects in the software itselfLeads privacy incident response and makes breach notification decisions
ChangesApplies approved changes, tests them where possible and records themDocuments software features and changesRequests and approves changes through named approvers
Software updatesReviews release notes and plans and applies updates with your approvalReleases software updates and security fixes on its own scheduleApproves update timing
Policy decisionsRecommends release, retention and exception settings with reference to HIPAA safeguardsNoneDecides the print policy, exceptions and what the logs keep

See how it works

A short walkthrough

Illustrative screens of how Moraph runs the service, with fictional sample data. They are not screens of PaperCut itself, which belongs to its vendor.

  1. Step 1

    The rollout tracker

    During implementation, each site has a row: devices, readers, exceptions and where it stands.

    SiteDevicesReaders fittedExceptions proposedStaff briefedStatus
    Main hospital, floors 1 to 3 (example)48486YesLive
    Main hospital, floors 4 to 6 (example)52504Yes2 readers faulty
    Outpatient clinic north (example)14141In progressTesting
    Imaging center (example)902NoPlanned
    Billing office (example)11110YesLive
    During implementation, each site has a row: devices, readers, exceptions and where it stands.

  2. Step 2

    The configuration baseline

    Release rules, log settings and exceptions are written down and approved by your privacy officer.

    Baseline v2 · Example Health (fictional)

    Status
    Awaiting approval
    Prepared by
    Moraph print engineer
    Approver
    Privacy officer
    Changes from v1
    3
    Open exceptions
    1 past review date

    Key settings

    • All general-purpose devices: badge release required
    • PIN release allowed only where no reader is fitted, pending replacement
    • Unreleased jobs deleted after the period set in the print policy
    • Scan to email limited to the user's own address
    Release rules, log settings and exceptions are written down and approved by your privacy officer.

  3. Step 3

    An exception request

    Devices that print without release need a reason, a compensating control and your privacy officer's approval.

    EX-0112 · Wristband printer, emergency department registration

    1. Exception requested: wristbands must print at registrationDepartment manager
    2. Compensating control proposed: printer inside staff-only areaMoraph print engineer
    3. Exception approved with review datePrivacy officer
    4. Device configured outside the secure queueMoraph print engineer
    5. Exception added to register and linked to approvalMoraph print engineer
    Devices that print without release need a reason, a compensating control and your privacy officer's approval.

  4. Step 4

    Issue triage

    Moraph investigates printing problems and escalates what needs your decision, with the evidence and a recommendation.

    Floor 5 · Jobs printing without release

    Reported by
    Charge nurse
    Device
    Floor 5 nurses' station (example)
    Finding
    Device added directly to workstations, bypassing the secure queue
    Users affected
    Floor 5 workstations
    Status
    Escalated to privacy officer

    Recommendation

    • Remove the direct queue from the affected workstations
    • Add a check for direct queues to the monthly review
    • Privacy officer to decide whether any follow-up is needed
    Moraph investigates printing problems and escalates what needs your decision, with the evidence and a recommendation.

  5. Step 5

    Administrator access review

    Everyone with administrative rights in PaperCut is listed for your privacy officer to confirm or remove.

    AccountOrganizationRoleLast usedDecisionStatus
    Admin 0141MoraphPrint engineerThis weekConfirmComplete
    Admin 0157MoraphPrint engineerThis monthConfirmComplete
    Admin 2210Your organizationIT administratorThis monthConfirmComplete
    Admin 2238Your organizationIT administratorNot used in 6 monthsRemovePending
    Admin 2301Your organizationReport viewerLast quarterNot decidedOverdue
    Everyone with administrative rights in PaperCut is listed for your privacy officer to confirm or remove.

  6. Step 6

    The monthly service review

    Moraph and your team go through what changed, what happened and what is still open.

    Service review · Sample month

    Changes applied
    6, all approved
    Issues raised
    11, 10 closed
    Devices on secure release
    134 of 140
    Open exceptions
    13
    Print record searches
    1, requested by privacy officer

    Actions agreed

    • Replace the two faulty readers on floor 5 with the device supplier
    • Review the exception past its review date
    • Start badge registration at the imaging center
    Moraph and your team go through what changed, what happened and what is still open.

Workflows

The principal workflows

  1. Print and release

    Staff print as they do today. PaperCut holds the job until they sign in at a device with their badge, so pages come out only when they are standing there, at whichever enabled device they choose.

    • Staff print from the EHR or another application to the secure queue
    • PaperCut holds the job against the user's identity
    • The user taps their badge at any enabled device
    • PaperCut lists their waiting jobs and releases the ones they choose
    • Jobs never released are deleted after the time your policy sets

  2. Exceptions

    Some printing cannot wait for a badge tap, such as wristband, label and specimen printers. These devices are listed as exceptions with a reason, an owner and a compensating control, and approved by your privacy officer.

    • Device or workflow proposed as an exception, with the reason
    • Moraph records the compensating control, such as a restricted location
    • Privacy officer approves or declines the exception
    • Approved exceptions are configured and recorded
    • Each exception is reviewed on the date your policy sets

  3. Investigate

    When a printed document is found in the wrong place or named in a complaint, the privacy officer can ask for the print record: who printed it, from which workstation, to which device and when it was released.

    • Privacy officer requests a print record search with the details known
    • Moraph searches PaperCut's logs within the agreed scope
    • Results returned to the privacy officer with the search recorded
    • Privacy officer decides on follow-up under your policy
    • Configuration changes that follow are made through the change process

  4. Operate

    Moraph monitors print servers, devices and badge readers, adds and retires devices, applies approved changes and reports on the service.

    • Moraph watches print server health, device status and release failures
    • Issues are triaged and escalated to your team where a decision is needed
    • Changes are requested by your team and approved by your named approver
    • Moraph applies and records each change
    • The monthly service review covers changes, issues and open actions

Roles and permissions

Who does what in the product

Each role below is a starting point. During implementation we set them up to match your teams, and every action anyone takes is recorded in the audit trail.

Privacy officer

Privacy officer, chief compliance officer, HIPAA privacy and security officer

Owns how printed patient information is protected and decides the release policy, exceptions and log settings.

Sees

  • The configuration baseline and the exception register
  • Print record search results they have requested
  • Change history, issues and service reports
  • Issues Moraph has escalated, with recommendations

Does

  • Approves the configuration baseline and changes to it
  • Approves or declines exceptions and sets their review dates
  • Decides how long unreleased jobs are kept and what the logs record
  • Requests print record searches for investigations
  • Attends the monthly service review and agrees actions
  • Requests evidence for audits

Cannot

  • Approve a change they requested themselves, where a second approver is named
  • Edit or delete the change history or PaperCut's logs
Approvals
Approves policy changes, exceptions and log settings; changes they request themselves are approved by a second named approver.
Notified about
Changes and exceptions waiting for approval, exceptions reaching their review date, and escalated issues.

IT administrator

Desktop support lead, print administrator, IT operations manager

Looks after users and workstations day to day and works with Moraph on devices, queues and changes.

Sees

  • Device and print server status
  • Requests and issues they or their team raised
  • The configuration baseline and change history

Does

  • Raises change requests for new devices, moves and queue changes
  • Handles first-line issues such as a badge that will not release jobs
  • Deploys print queues to workstations with Moraph's guidance
  • Coordinates device installs with the device supplier and Moraph

Cannot

  • Approve exceptions or log settings
  • Search print records for an investigation
Approvals
Changes they request are approved by the privacy officer or another named approver.
Notified about
Outcomes of their requests, device and server issues affecting users, and planned changes.

Department manager

Nurse manager, clinic manager, registration supervisor, HIM manager

Makes sure the department can print what it needs while keeping patient documents secure.

Sees

  • Devices and exceptions in their area
  • Release activity and unreleased job counts for their area
  • The status of their requests

Does

  • Requests new devices, moves or exceptions for the department
  • Reports printing problems through IT
  • Reminds staff to use secure release and to collect their jobs
  • Confirms exceptions in their area at review time

Cannot

  • Approve exceptions or configuration changes
  • See other users' print records
Approvals
Exceptions and device changes they request are approved by the privacy officer.
Notified about
Outcomes of their requests and exceptions in their area due for review.

Staff member

Nurses, physicians, registration and clinic staff, other employees who print

Prints and releases their own documents at a device of their choice.

Sees

  • Their own held jobs at the device
  • Devices on the secure queue near them

Does

  • Prints to the secure queue
  • Releases or deletes their own jobs at a device with their badge
  • Registers their badge at a device where your policy allows

Cannot

  • Release or see other users' jobs
  • Change any settings
Approvals
None.
Notified about
Nothing by default; held jobs are shown at the device.

Moraph print engineer

Moraph print engineer, Moraph managed platform engineer

Builds and maintains the PaperCut configuration and keeps servers, devices and badge readers working.

Sees

  • PaperCut configuration, queues, devices and logs
  • Print server, device and badge reader health
  • Approved change requests and the configuration baseline

Does

  • Applies approved changes to queues, devices, rules and exceptions
  • Adds and retires devices and badge readers
  • Runs print record searches requested by the privacy officer, within scope
  • Triages issues and escalates those that need a decision
  • Plans and applies PaperCut updates with your approval

Cannot

  • Apply a change that has not been approved, except under the agreed emergency procedure
  • Search print records without a request from the privacy officer
  • Approve their own changes or any exception
Approvals
Every change they apply is approved in advance by your named approver, or reported straight away when made under the emergency procedure.
Notified about
Server and device alerts, release failures and approved changes ready to apply.

Moraph service manager

Moraph service manager, Moraph customer success lead

Runs the service relationship, tracks requests and issues and reports on how the service is performing.

Sees

  • Requests, issues and changes and their status
  • Service reports and the exception register
  • Open actions from earlier service reviews

Does

  • Prepares and chairs the monthly service review
  • Tracks requests and escalations through to closure
  • Coordinates with PaperCut on platform defects and with device suppliers on hardware
  • Prepares evidence packs your team requests

Cannot

  • Change the PaperCut configuration
  • See print record search results
Approvals
None; their reports and minutes are accepted by your privacy officer.
Notified about
Escalations, overdue requests and vendor notices affecting you.

Auditor (read-only)

Internal auditor, external auditor, compliance reviewer (under temporary access)

Reviews the print controls and their evidence without being able to change anything.

Sees

  • The configuration baseline and exception register
  • Change history and approvals
  • Service reports and evidence packs within the scope granted

Does

  • Reads records and reports within their scope
  • Exports evidence they have been given access to, with each export logged

Cannot

  • Change, approve or delete anything
  • See individual print records unless the privacy officer includes them in scope
  • Keep access after it expires
Approvals
Their access is approved by the privacy officer, with a scope and an end date.
Notified about
Nothing by default.

Permissions at a glance

ActionPrivacy leadIT adminDept. managerStaffMoraph eng.Moraph serviceAuditor
Release print jobsOwn work onlyOwn work onlyOwn work onlyOwn work onlyNo accessNo accessNo access
Approve the configuration baselineApprovesNo accessNo accessNo accessNo accessNo accessView only
Request a configuration changeFullFullOwn work onlyNo accessNo accessNo accessNo access
Apply a configuration changeApprovesNo accessNo accessNo accessFullNo accessNo access
Approve a device exceptionApprovesNo accessNo accessNo accessNo accessView onlyView only
Add or retire a deviceApprovesView onlyNo accessNo accessFullNo accessNo access
Change log and retention settingsApprovesNo accessNo accessNo accessFullNo accessNo access
Search print records for an investigationApprovesNo accessNo accessNo accessFullNo accessNo access
Register a badge to a userView onlyFullNo accessOwn work onlyFullNo accessNo access
Grant PaperCut administrator rightsApprovesNo accessNo accessNo accessFullNo accessNo access
View change history and service reportsView onlyView onlyNo accessNo accessView onlyView onlyView only
  • Full
  • Own work only
  • Approves
  • View only
  • No access

How access is controlled

  • Moraph engineers apply changes; your organization approves them. Nobody approves a change or exception they requested themselves when a second approver is named.
  • Print record searches are made only at the privacy officer's request, within the scope they set, and each search is recorded.
  • Moraph staff use named, individual administrator accounts in PaperCut with only the rights the service needs. There are no shared administrator accounts.
  • Roles are agreed during implementation and can be limited by site or department. Auditors get read-only evidence with a defined scope and end date.

Features

What it does

Badge release

PaperCut holds each job until the user signs in at a device with their badge, or with a PIN where your policy allows.

Print at any enabled device

A held job can be released at any device on the secure queue, so staff are not tied to the printer they chose when they printed.

Unreleased job deletion

Jobs that are never released are deleted after a period your policy sets, so forgotten documents do not wait indefinitely.

Print activity log

PaperCut records who printed, from which workstation, to which device and when, for use in privacy investigations.

Document name handling

How much of each document name is kept in the logs is configured with your privacy officer, within the options PaperCut provides.

Exception register

Label, wristband and other devices that print without release are listed with their reason, owner, compensating control and review date.

Print rules

PaperCut applies rules your teams approve, such as defaulting to double-sided or black and white, or adding a watermark to selected queues.

Scan controls

On multifunction devices, scanning can require sign-in and be limited to approved destinations, such as the user's own email or a set folder.

Badge registration

Badges are linked to user accounts from your badge system or directory, and new staff can register a badge at the device where your policy allows.

Device and server monitoring

Moraph watches print servers, devices and badge readers and acts on failures before staff are left unable to print.

Device lifecycle

New devices are added to the secure queue and retired devices are removed, under your change process, so the configuration matches what is on the floor.

Monthly service review

Changes, issues, exceptions, release activity and open actions reviewed with your privacy officer and IT lead.

Integrations

How it connects to your systems

Connects toHowWhat flows
DirectoryPaperCut takes user accounts and groups from your directory, so printing follows the same identities as the rest of your systems.In: user accounts and group membership.
Badge systemBadge numbers are linked to user accounts from your badge or access control system, by file or directory attribute, or registered at the device.In: badge numbers linked to users.
EHR and clinical printingPrint queues used by your EHR and other clinical applications are pointed at the secure queue or at approved exception devices, tested with your application team.In: print jobs from clinical applications.
Multifunction devicesPaperCut's software on supported devices provides badge sign-in, job release and scan controls.In and out: release requests, held jobs and scan destinations.
Security monitoringPaperCut and print server logs can be forwarded to your security monitoring or log platform where you want them kept alongside other logs.Out: print activity and administrator logs.
Single sign-onAdministrators and managers sign in to PaperCut's web interface through your identity provider where the deployment supports it.In: user identity and group membership.
Moraph service recordsRequests, changes, issues, exceptions and service reviews are tracked in Moraph's service records and available to your team.Out: change, ticket, exception and service review records.

Each integration is confirmed in discovery and specified in the design. See how an engagement progresses.

Security and privacy

How your data is protected

Named Moraph administrators

Moraph staff work in PaperCut with individual accounts and only the administrative rights the service needs; there are no shared accounts.

Role-based access

What each person at your organization and at Moraph can see and do follows their role; requesting a change is separate from approving it.

Business associate agreement

Print jobs and logs can contain protected health information, so Moraph works under a business associate agreement with you.

Complete audit trail

PaperCut records print and administrator activity, and Moraph's change record links each change and each print record search to its request and approval.

Encryption and keys

Service records Moraph holds are encrypted, with keys Moraph staff cannot use without explicit, time-bound authorization.

Audited company-wide

Moraph is audited to SOC 2 Type II and ISO/IEC 27001 across the company, including the teams that run this service. PaperCut's own commitments cover its software.

Company-wide controls, independent audits (SOC 2 Type II and ISO/IEC 27001) and data residency are described in our Trust Center, where you can request the evidence pack.

Reporting

What you can report on

11 standard reports, grouped by who uses them. Each shows who it is for, how it can be broken down, how it is delivered and what it is used for. The data behind them is also available to your own reporting tools.

Control coverage

Secure release coverage

For privacy officer, IT lead

Devices on the secure queue, devices on the exception register and devices not yet configured, by site.

Break down by
Site, Department, Device type, Status
Delivered as
Monthly PDF; CSV export
Used for
Showing where secure release is in place and where gaps remain.

Exception register

For privacy officer, auditors

Each exception with its reason, owner, compensating control, approver and review date.

Break down by
Site, Device type, Owner, Review status
Delivered as
Live view in Moraph's service records; PDF export
Used for
Reviewing exceptions on time and evidencing that each was approved.

Unreleased jobs

For privacy officer, department managers

Jobs held but never released and deleted under policy, by area, to show where staff print and do not collect.

Break down by
Site, Department, Period
Delivered as
PaperCut reports; monthly PDF
Used for
Targeting reminders and spotting workflows that need a different device.

Service operations

Change log

For privacy officer, IT lead, auditors

Every change to queues, devices, rules, exceptions and settings, with who requested, approved and applied it.

Break down by
Change type, Requester, Approver, Date
Delivered as
Live view; CSV and PDF export
Used for
Showing that changes were requested, approved and recorded.

Requests and issues

For iT lead, Moraph service manager

Requests and issues raised, their status, and how each was resolved or escalated.

Break down by
Type, Site, Status, Period
Delivered as
Live view; monthly PDF
Used for
Tracking open work and spotting recurring problems.

Device and reader health

For iT lead, Moraph service manager

Devices and badge readers with faults, time out of service and repairs raised with suppliers.

Break down by
Site, Device, Fault type, Period
Delivered as
Monthly PDF; CSV export
Used for
Following up suppliers and planning device replacement.

Usage

Print volumes

For iT lead, finance

Pages printed by site, department and device, including color and single-sided printing.

Break down by
Site, Department, Device, Period, Color or mono
Delivered as
PaperCut reports; CSV export
Used for
Managing print costs and right-sizing the device fleet.

Scan activity

For privacy officer, IT lead

Scans made at multifunction devices by destination type, and any scans blocked by the configured rules.

Break down by
Site, Destination type, Period
Delivered as
PaperCut reports; monthly PDF
Used for
Checking that scanned patient documents go only to approved destinations.

Privacy and audit

Print record search log

For privacy officer

Each print record search: who asked for it, why, the scope, who ran it and when the results were given.

Break down by
Requester, Date, Reason, Scope
Delivered as
Live view; PDF export
Used for
Showing that print records were searched only when authorized.

Administrator access review

For privacy officer, IT lead

Everyone with administrative rights in PaperCut, at your organization and at Moraph, for confirmation or removal.

Break down by
Organization, Role, Last used
Delivered as
Scheduled PDF
Used for
Keeping administrative access limited to the people who need it.

Service review summary

For privacy officer and IT leadership

The month's changes, issues, exceptions, coverage and agreed actions.

Break down by
Month, Topic, Action owner
Delivered as
PDF after each service review
Used for
Keeping leadership informed and holding both sides to agreed actions.

Exports, access and evidence

  • Service reports are prepared by Moraph from PaperCut's reports and logs and from Moraph's own change and ticket records.
  • PaperCut's own reports remain available in the software to the administrators you authorize.
  • Reports respect each viewer's role: department managers see their own areas, and individual print records go only to the privacy officer or people they authorize.
  • Print and administrator logs can be forwarded to your log platform for retention beyond what PaperCut keeps.
  • Requesting and exporting an evidence pack or a print record search is itself recorded, so you can show what was given to whom.

Deployment

Where and how it runs

Licences through Moraph

Moraph resells PaperCut licences and runs the service as one, subject to PaperCut's terms.

Your existing PaperCut system

If you already license PaperCut, Moraph reviews the current configuration against a new baseline and takes over its operation.

Co-managed

Your IT team keeps some tasks, such as first-line support or queue deployment to workstations, and Moraph runs the rest; the split is written into the responsibilities for the service.

Security controls, independent audits and data residency are set out in our Trust Center. Engagement models and what drives a quotation are on Working with Moraph.

Implementation

What a rollout involves

The general phases are on Working with Moraph. For this product, they involve the following.

Discovery

We inventory devices, print servers, queues, badge readers and the applications that print patient documents, with your IT, privacy and clinical teams.

Baseline design

Release rules, unreleased job deletion, log settings, print rules and proposed exceptions are designed and approved by your privacy officer.

Build

PaperCut is installed or configured to the baseline, connected to your directory and badge data, and set up on supported devices and readers.

Clinical application testing

EHR and other clinical print queues are tested with your application team, including label and wristband printing that stays on exception devices.

Site rollout

Sites and departments move to secure release in waves, with staff communications, badge registration and floor support agreed for each wave.

Handover to operations

Change process, approvers, escalation contacts, fallback printing and reporting are agreed, and the service moves into day-to-day operation.

Limitations

What it does not do

Worth knowing before you evaluate it.

  • Moraph is not PaperCut. PaperCut provides the software, and its own support commitments, roadmap and release schedule apply, as do any outages of services it hosts.
  • PaperCut licences are subject to PaperCut's terms, and some capabilities depend on the edition licensed and the device model.
  • Secure release works only on supported devices with supported badge readers. Devices that cannot support it are replaced, restricted or recorded as exceptions.
  • Some clinical printing, such as wristbands, labels and specimen printing, usually cannot wait for a badge tap; it stays on exception devices with compensating controls.
  • Moraph does not supply, lease or repair print devices unless agreed separately; hardware faults go to your device supplier.
  • Secure release protects pages at the printer. It does not stop an authorized user from mishandling a document after collecting it.
  • Moraph configures controls with reference to HIPAA safeguards, but your organization decides whether they are adequate and makes all privacy and breach notification decisions.
  • Fax, mail and paper records management are outside this service.

Evaluation checklist

What to test in a demonstration or pilot

Questions worth putting to us, and to any other vendor you are considering.

  1. List your devices and badge readers and check which can support secure release
  2. Identify the clinical printing that cannot wait for a badge tap and how it would be handled
  3. Walk through a print record search from the privacy officer's request to the recorded result
  4. Review a sample configuration baseline and exception register
  5. Ask how unreleased jobs, log settings and document names are handled and who decides
  6. Confirm the split of responsibilities between Moraph, PaperCut, your device supplier and your IT team

Questions

Frequently asked questions

Do we buy PaperCut from Moraph or from PaperCut?

Either. Moraph can resell the licences, or run a system you already license. In both cases PaperCut's terms apply.

Will our existing printers work?

Many common multifunction devices and printers are supported, but it depends on the model and its badge reader. Discovery lists each device and what it would need.

What about wristband and label printers?

These usually stay outside secure release because the work cannot wait. They are recorded as exceptions with a compensating control and approved by your privacy officer.

Can Moraph see what our staff print?

Moraph engineers can reach PaperCut's logs to run the service, under a business associate agreement. Print records are searched for an investigation only at your privacy officer's request, and each search is recorded.

How is it priced?

PaperCut licences are priced under PaperCut's terms, and the managed service and implementation are quoted separately. See Working with Moraph for what drives a quotation.

Can we take the service back in-house?

Yes. The system and its configuration are yours; at the end of the agreement Moraph hands over the baseline, documentation, exception register and change history and removes its administrator accounts.

Next steps

Evaluate Secure Printing

Book a demonstration

See the product working with sample data, focused on your workflows.

Request a demonstration

Request a technical briefing

Architecture, integrations, security and hosting, with our engineers and your technical team.

Request a briefing

Factsheet

This page on two sides, to share with colleagues or add to your evaluation file.

Open the factsheet

Buying through a formal procurement? See How to buy for purchasing routes, accessibility conformance reports and company information. Documentation: Secure Printing guides on docs.moraph.com (getting started and security guides are public; setup, administration and integration guides are for client accounts). Support: Secure Printing support guide.

Related products