Establishing secure connection…Loading editor…Preparing document…

MC 315 Authorization Form

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

STATE OF MICHIGAN
AUTHORIZATION FOR RELEASE OF MEDICAL INFORMATION

Approved, SCAO
Original - Records custodian
1st copy - Requesting party
2nd copy - Patient
STATE OF MICHIGAN
JUDICIAL DISTRICT
JUDICIAL CIRCUIT
COUNTY PROBATE
AUTHORIZATION FOR RELEASE
OF MEDICAL INFORMATION
CASE NO.
Court address Court telephone no.
Plaintiff
v
Defendant
Probate In the matter of

1. Date of birth

2. I authorize

to release

to

3. I understand that unless I expressly direct otherwise:

a) the custodian will make the medical information reasonably available for inspection and copying, or

b) the custodian will deliver to the requesting party the original information or a true and exact copy of the original information accompanied by the certificate on the reverse side of this authorization.

I understand that medical information may include records, if any, on alcohol and drug abuse, psychology, social work, and information about HIV, AIDS, ARC, and any other communicable disease.

4. This authorization is valid for 60 days and is signed to make medical information regarding me available to the other party(ies) to the lawsuit listed above for their use in any stage of the lawsuit. The medical information covered by this release is relevant because my mental or physical condition is in controversy in the lawsuit.

5. I understand that by signing this authorization there is potential for protected health information to be redisclosed by the recipient.

6. I understand that I may revoke this authorization, except to the extent action has already been taken in reliance upon this authorization, at any time by sending a written revocation to the doctor, hospital, or other custodian of medical information.

Date
Signature
Address
Name (type or print) (If signing as Personal Representative, please state under what authority you are acting)
City, state, zip
Telephone no.

MC 315 (3/06) AUTHORIZATION FOR RELEASE OF MEDICAL INFORMATION

45 CFR 164.508, MCL 333.5131(5)(d), MCL 333.26265,
MCR 2.506(D)(1)(b), MCR 2.314

CERTIFICATE

1. I am the custodian of medical information for

Organization

2. I received the attached authorization for release of medical information on .

Date

3. I have examined the original medical information regarding this patient and have attached a true and complete copy of the information that was described in the authorization.

4. This certificate is made in accordance with Michigan Court Rule.

I declare that the statements above are true to the best of my information, knowledge, and belief.

Date
Signature
Name (type or print)
Address
City, state, zip
Telephone no.
Enter text✕

What the MC 315 Authorization Form Is and when it’s used

The MC 315 Authorization Form is a formal U.S. administrative authorization used to grant a named person or entity permission to act on behalf of another party for a specific, limited purpose. Typical uses include authorizing third-party access to records, permitting an agent to file documents, or delegating signature authority for a single transaction. The form records the scope of authority, identifies parties, and sets effective dates and limits. Proper completion establishes a clear audit trail and helps organizations comply with document retention and authentication requirements under ESIGN and applicable state law.

Why completing an MC 315 matters for accuracy and compliance

A correctly completed MC 315 clarifies authority, reduces processing delays, and creates an auditable record that supports enforcement or dispute resolution. Using an e-signed, retained copy preserves attribution and satisfies ESIGN/UETA requirements for most commercial transactions.

Why completing an MC 315 matters for accuracy and compliance

Which organizations and roles typically use the MC 315

Common users span several sectors that need delegated authority recorded formally.

  • Real Estate teams and brokers who authorize agents to submit filings and close transactions.
  • Healthcare administrators and business associates needing written patient-authorized access under HIPAA.
  • Financial services and accounting teams granting tax preparers or agents limited filing authority.

Internal approvers, legal counsel, and compliance officers commonly review the completed MC 315 before acceptance.

Step-by-step: complete and validate the MC 315

Follow this sequence to prepare a compliant MC 315 and reduce rejection risk.

  • 01
    Gather documents: Collect IDs, entity formation docs, and prior authorizations for verification.
  • 02
    Fill core fields: Enter names, scope, dates, and contact details carefully.
  • 03
    Verify identity: Use government ID, KBA, or multi-factor methods as required.
  • 04
    Sign and distribute: Apply signatures, obtain notary/witness if required, then retain copies.

How to set up a digital MC 315 workflow

Configure the online workflow to capture required fields, signer authentication, and archival copies before sending for signature.

Field Configuration
Authorization Scope Mandatory text field with character limits and dropdown templates
Signature Allow ESIGN-compliant eSignatures; enable visible signature and date
Authentication Use email + SMS OTP or KBA for identity assurance
Retention Auto-save signed PDF/A copy and audit trail

Where to send or file the completed MC 315

The destination depends on the transaction type and recipient requirements; confirm the correct recipient and method before sending.

  • Internal Records: Store original signed copy in your legal or compliance repository.
  • Third-Party Recipient: Deliver to the named agency, counterparty, or service provider per their submission rules.
  • Regulators: File with the regulatory office only if the authorization form is required by rule.
  • Email or Portal: Use secure portals or encrypted email when sending sensitive authorizations.

Technical considerations for eSigning and eSubmission

Choose a platform that supports required authentication, audit trails, and secure file formats for long-term retention.

  • File formats: PDF, PDF/A, DOCX supported
  • Integrations: Salesforce, NetSuite, Microsoft 365
  • Authentication: Email, SMS OTP, KBA

Timing: processing expectations and common timelines

Processing times depend on recipient procedures; plan for verification and any manual review steps when setting expectations.

Immediate Acknowledgment:

Automated systems often confirm receipt within minutes

Verification Window:

Identity or document checks commonly take 1–5 business days

Regulatory Filing:

Some agencies require 7–30 business days for formal acceptance

Amendments:

Allow 5–10 business days for revised forms to be processed

Record Availability:

Signed copies should be accessible to parties immediately after completion

Key milestones from preparation to filing

Track these milestones to manage approvals and avoid processing delays.

01

Draft and Review

Complete fields and get internal legal review before signature.

02

Identity Verification

Authenticate signer using ID, KBA, or multifactor methods as required.

03

Signature Capture

Obtain signatures and notary or witness elements if mandated.

04

Distribution and Archive

Send copies to recipients and store signed records securely.

Common mistakes to avoid when preparing an MC 315

  • Using informal or ambiguous scope language that fails to define permitted actions clearly.
  • Mismatched names between the authorization and supporting IDs causing identity verification failures.
  • Skipping required notarization or witness lines when a recipient explicitly requires them.
  • Failing to retain an audit trail or signed PDF/A copy, undermining long-term reproducibility.

Consequences and regulatory risks of errors

Rejection: Form refused
Processing Delay: Service or filing postponed
Contract Invalid: Authority contested
Regulatory Fine: Agency penalties possible
Backup Withholding: Tax consequences may follow
Privacy Breach: Sensitive data exposure

Security and compliance basics for MC 315 handling

Encryption: AES-256 at rest
Transport: TLS 1.2/1.3 in transit
Audit Trail: IP, timestamp, action log
HIPAA: BAA required for PHI
ESIGN / UETA: Legal validity framework
SOC 2: Type II available

Frequently asked questions about the MC 315 Authorization Form

Answers to common questions on validity, eSigning, notarization, corrections, and revocation to help avoid common pitfalls.


Need help? Contact support

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