Establishing secure connection…Loading editor…Preparing document…

Healthcare DICOM Agreement

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

HEALTHCARE DICOM AGREEMENT

Patient Name:   Date of Birth:   Medical Record Number:

PARTIES AND PURPOSE

Sender / Custodian of Records (Facility Name):

Recipient / Requesting Party (Name or Organization):

Purpose of Disclosure: Treatment / Continuity of Care   Personal Use   Legal / Litigation   Research (separate IRB/consent may be required)

DEFINITIONS

For purposes of this Agreement, "DICOM Data" means medical image data and associated metadata stored or transmitted in the Digital Imaging and Communications in Medicine (DICOM) format. "Protected Health Information" or "PHI" has the meaning provided under applicable privacy laws and includes any DICOM header fields or other data that can reasonably be used to identify the patient.

SCOPE OF RECORDS TO BE TRANSMITTED

Select modality types and provide timeframe for the requested DICOM studies:

CT   MRI   X-ray   Ultrasound   PET   Other:

Date range of studies: From to .

FORMAT, TRANSMISSION, AND SECURITY

Format requested: Native DICOM (with header metadata)   Embedded JPEG/JPEG2000   Other:

Transmission method: Secure DICOM Send / PACS Transfer   Encrypted Portal Transfer   Physical Media (CD / USB)   Other:

If physical media, handling instructions:

DE-IDENTIFICATION / PHI HANDLING

Release of PHI in DICOM header: Release full headers including patient identifiers   De-identified DICOM (remove direct identifiers per standard)   Limited dataset (retain limited indirect identifiers)

Patient acknowledgment: By signing this Agreement, the patient understands that once DICOM files are disclosed to the Recipient they may be subject to redisclosure and may no longer be protected by the Sender's policies.

AUTHORIZATION, REVOCATION, AND EXPIRATION

Authorization: I authorize the Sender to disclose the DICOM Data described herein to the Recipient for the purpose(s) stated above. This authorization is voluntary and is not a condition of treatment, payment, enrollment, or eligibility for benefits.

Right to revoke: This authorization may be revoked by submitting a written revocation to the Sender's records custodian. Revocation will not affect disclosures already made in reliance on this authorization prior to receipt of the revocation.

Expiration: Unless revoked earlier, this authorization will expire on: . If no date is provided, authorization will expire six months from the date of signature.

FEES, LIABILITY, AND INDEMNIFICATION

Fees: The Recipient or Patient may be charged reasonable reproduction and transmission fees in accordance with the Sender's policies. Charges must be disclosed in advance upon request.

Liability: The Sender will use commercially reasonable measures to transmit the DICOM Data securely. The Sender is not responsible for unauthorized access or disclosure that occurs after delivery to the Recipient or for the Recipient's handling of the data.

Indemnification: The Recipient agrees to indemnify and hold harmless the Sender and its agents from any claims, liabilities, losses, or expenses arising from the Recipient's misuse or unauthorized disclosure of the DICOM Data.

BREACH NOTIFICATION

In the event of an unauthorized acquisition, access, use, or disclosure of unencrypted DICOM Data constituting a breach, the party discovering the breach shall promptly notify the other party in writing and cooperate in any required mitigation and notification efforts, consistent with applicable law.

NOTICES AND CONTACTS

ADDITIONAL INSTRUCTIONS

CERTIFICATION AND ACKNOWLEDGMENT

I certify that I am the patient named above or the patient's legal representative with authority to sign on the patient's behalf. I have read and understand the terms of this Healthcare DICOM Agreement. I understand the purposes for which the DICOM Data will be used and the potential for redisclosure by the Recipient. I authorize the release of the DICOM Data as specified in this Agreement.

Signature

Patient Printed Name:

Signature:

Date:

If signed by legal representative, print name and relationship:

Witness or Staff Printed Name:

Enter text✕

What the Healthcare DICOM Agreement Covers

A Healthcare DICOM Agreement is a written contract that governs electronic sharing, storage, and use of medical imaging files using the DICOM standard. It defines permitted recipients, security controls, metadata handling, responsibilities for de-identification, and permitted use cases such as treatment, second opinions, research, or tele-radiology. The agreement also addresses consent, data retention, audit logging, breach notification procedures, and any business associate obligations required under HIPAA when PHI is involved.

Why a DICOM Agreement Matters for Care Continuity

A clear agreement reduces legal and clinical risk by setting technical and privacy expectations for exchanging diagnostic images. It supports HIPAA compliance, clarifies responsibilities, and helps ensure images remain usable and auditable across vendors and PACS systems.

Why a DICOM Agreement Matters for Care Continuity

Typical parties who sign or manage DICOM agreements

Healthcare organizations, imaging centers, teleradiology vendors, and research institutions commonly enter these agreements to enable image exchange.

  • Hospitals and health systems — IT and privacy teams coordinate technical, legal, and operational requirements for cross-system image sharing.
  • Independent imaging centers and radiology groups — define delivery formats, turnaround times, and responsibilities for studies and reports.
  • Research organizations and imaging core labs — require de-identification protocols, IRB compliance, and permitted downstream uses.

Who typically signs and what they represent

Hospital IT Director

Signs on behalf of the hospital for technical controls and integration commitments; coordinates with privacy officers for HIPAA compliance and with PACS/VNA administrators for format compatibility.

Imaging Vendor Executive

Signs for the vendor to accept responsibilities for secure transport, storage, de-identification options, and support SLAs; may also commit to audit logging and incident reporting timelines.

Core elements to include in a DICOM agreement

A well-drafted Healthcare DICOM Agreement balances clinical interoperability, data security, and legal compliance. Key clauses address data scope, format, authentication, retention, breach handling, and liability allocation.

Scope of Data

Define exactly which imaging modalities, associated reports, annotations, and metadata are covered and whether derived data is included.

Access & Authentication

Specify credentialing, multi-factor options, API keys or SAML/SSO requirements, and authorized user roles for viewing and exporting images.

Transmission & Encryption

Require encrypted transport (TLS 1.2/1.3) and at-rest encryption (AES-256) along with integrity checks and checksums where applicable.

De-identification Rules

State the de-identification standard (HIPAA safe harbor or expert determination), what fields are removed or retained, and who performs the process.

Audit & Logging

Obligate maintenance of tamper-evident audit trails recording access, export, timestamps, and signer identity for forensic review.

Breach Notification

Set notification timelines, investigation cooperation, forensic obligations, and cost-sharing for remediation consistent with HIPAA breach rules.

Step-by-step: executing a Healthcare DICOM Agreement

Follow a consistent sequence from negotiation through execution to ensure technical and legal readiness before data exchange begins.

  • 01
    Draft Terms: Define scope, security, retention, and liability terms with clinical and privacy stakeholders.
  • 02
    Technical Review: Validate DICOM transfer parameters, AE titles, port configurations, and expected file naming conventions.
  • 03
    Legal & Compliance: Obtain HIPAA review, include BAA if PHI is shared, and confirm any state-specific requirements.
  • 04
    Sign and Distribute: Execute by authorized signers and distribute fully executed copies to operations and IT teams.

Typical exchange workflow for DICOM-enabled sharing

A standard exchange moves from request and authorization through secure transfer, confirmation, and logging to maintain chain-of-custody and clinical utility.

  • Request: Clinician or system requests imaging via secure portal or API with patient identifier.
  • Authorization: Validate consent or legal authority and confirm allowed recipients and purposes.
  • Transfer: Transmit using encrypted DICOM protocols or a secure API endpoint with integrity checks.
  • Confirmation: Confirm receipt, validate image integrity, and log the transfer in an audit trail.

Key workflow settings to configure before exchange

Standardize these settings in your implementation plan to reduce errors during initial transfer and ongoing operations.

Field Configuration
Authentication SAML/SSO, API keys, or MFA per organizational policy
Audit Trail Enable immutable logs with timestamps and user attribution
BAA Requirement Execute a Business Associate Agreement when PHI is transmitted
File Formats Support standard DICOM; permit PDF/JPEG for reports and snapshots

Technical and platform integration notes

Confirm platform compatibility, integration endpoints, and supported file types before signing or enabling exchange.

  • Integrations: Verify compatibility with PACS, VNA, EHR and integration middleware like HL7 interfaces
  • Formats: Support for DICOM standard plus PDF and DOCX for associated reports
  • Authentication: Use token-based API auth, SSO, or MFA depending on risk profile

Essential security and compliance checkpoints

Encryption: TLS 1.2/1.3; AES-256 at rest
Audit Logs: Tamper-evident, with timestamps
BAA: Business Associate Agreement required
Authentication: MFA or SAML/SSO recommended
Access Controls: Role-based access enforced
Record Retention: Retained per HIPAA and state rules

Common preparation mistakes to avoid

  • Not specifying exact DICOM attributes and transfer syntaxes causes incompatibility and failed imports between PACS implementations.
  • Failing to attach a signed BAA when PHI is transmitted can expose both parties to HIPAA enforcement and civil liability.
  • Omitting retention and disposition language leads to uncertainty about archival responsibilities and increases risk during audits.
  • Using informal consent language without referencing HIPAA-authorized disclosures or patient authorization can invalidate downstream sharing permissions.

Potential legal and operational risks

HIPAA Fines: Civil and criminal penalties
Data Breach Costs: Notification and remediation expenses
Clinical Harm: Delayed or incorrect diagnosis risk
Contract Liability: Indemnity and damages exposure
Operational Downtime: Integration failures and service delays
Regulatory Action: State attorney general enforcement

Key timelines and response deadlines

Certain legal and operational timelines affect when data must be provided, retained, or reported. Build these into SLAs and monitoring.

Patient Access Response:

HIPAA requires access within 30 days (45 CFR 164.524)

Breach Notification:

Timely reporting per HIPAA and state laws; federal minimums apply

RON Record Retention:

Audio-video records typically retained 5–10 years per state RON rules

Technical Acceptance Testing:

Complete validation before go-live; typical window 1–4 weeks

Retention Review:

Periodic reviews aligned with record retention policy

Milestones from negotiation to live exchange

A concise timeline keeps legal, clinical, and IT teams aligned and highlights go/no-go checkpoints.

01

Negotiation

Agree scope, security, and liability terms with stakeholders

02

Technical Onboarding

Configure endpoints, credentials, and test data exchanges

03

Legal Execution

Sign agreement and any required BAAs or consents

04

Go-Live

Begin monitored production exchange and confirm audits

eSignature vendor snapshot for Healthcare DICOM agreements

A comparison of typical vendor price points and features relevant to healthcare workflows; signNow is listed first per standard vendor ordering.

signNow DocuSign Adobe Sign PandaDoc HelloSign
Starting Price $8/user/mo $15/user/mo $14/user/mo $19/user/mo $15/user/mo
Free Trial 7-day free trial Varies by vendor Varies by vendor Varies by vendor Varies by vendor
Bulk Send Yes (Business Premium) Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes (BAA available) Yes Yes No No
Envelope Cap No cap 100 envelopes/user/year Varies by plan Varies by plan Varies by plan

Real-world examples of DICOM agreement use

These concise case notes illustrate how organizations typically use a Healthcare DICOM Agreement to enable secure image exchange.

Fertility Centers of Illinois

A regional fertility center needed interoperable image transfer for remote consultations.

  • They required a BAA plus de-identification for research uses.
  • The agreement clarified responsibilities, reduced transfer errors, and established a consistent audit trail for clinical review and compliance.

Optica Ventures LLC

A small imaging referral network required standardized DICOM export and secure viewer access.

  • They set technical endpoints and SLAs for turnaround.
  • The documented agreement reduced onboarding time for new partners and ensured consistent image integrity and metadata mapping across systems.

Frequently asked questions about Healthcare DICOM Agreements

Answers to common legal, technical, and operational questions that arise when preparing, executing, and managing DICOM agreements.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users