Public Website
Public forms and general website channels are for business inquiries. Patient-identifying information and clinical records should not be submitted through public inquiry forms.
UM Physician Advisors separates public business communications from patient-specific clinical-review information. When protected health information is required for an authorized engagement, information exchange follows the applicable client workflow, governing agreement, privacy requirements, and appropriate safeguards.
Public forms and general website channels are for business inquiries. Patient-identifying information and clinical records should not be submitted through public inquiry forms.
Patient-specific review information is exchanged through client-approved channels established for the authorized engagement and review purpose.
Privacy, access, permitted uses, information exchange, retention, and related responsibilities are governed by the applicable relationship, agreements, and requirements.
The public website supports business communication. Patient-specific clinical review begins only within the approved client workflow.
Use public website channels for consultation, contracting, service questions, and other non-patient-specific business communication.
When a contracted review requires protected health information, information is handled within the applicable client relationship and authorized workflow.
Information handling should be defined before patient-level review begins and remain aligned to the authorized purpose throughout the engagement.
Patient-specific clinical information is exchanged through client-approved channels established for the review program—not through the public business-inquiry form.
When UM Physician Advisors functions as a business associate, PHI is handled within the applicable HIPAA requirements and Business Associate Agreement.
Information access and exchange should be limited to the authorized review purpose and aligned with applicable minimum-necessary requirements and exceptions.
Clinical-information workflows should incorporate appropriate administrative, technical, and physical safeguards, with defined access and accountability responsibilities.
The engagement should define applicable notification, escalation, investigation, and response responsibilities for privacy or security events.
Record retention, return, destruction, and disposition expectations should be defined according to the governing agreement and applicable requirements.
If another party creates, receives, maintains, or transmits protected information as part of an authorized engagement, applicable downstream privacy, security, contractual, and Business Associate requirements should be addressed before that workflow is used.
Clarify what information the party may access, why access is required, and what responsibilities apply to that role.
Use only the systems, channels, and information-exchange pathways authorized for the engagement.
Address applicable confidentiality, privacy, security, Business Associate, retention, and incident obligations in the governing arrangements.
Where the HIPAA minimum-necessary standard applies, reasonable efforts should limit PHI used, disclosed, or requested to what is necessary for the intended purpose, subject to applicable exceptions. Access should also be aligned to the individual’s authorized role and review responsibilities.
Review the quality, compliance, coverage, patient-status, and medical-necessity frameworks that support physician review.
Discuss review scope, secure information exchange, coverage needs, and operational requirements for an authorized engagement.