Service and information map
Record customer systems, provider tools, staff access and external parties. Identify unresolved role or contractual questions.
A Philippine healthcare support team needs to know which decisions belong to the US customer and which remain with the provider. CyberVantage360 helps define those boundaries, assess risks and translate findings into practical controls. Give staff and supervisors clear instructions for routine work, exceptions and suspected disclosures.
HHS distinguishes covered entities, business associates and relevant subcontractors. Determine the role for the actual Philippine service; serving a healthcare customer does not make every local organisation a covered entity.
Follow health information through application access, quality review, calls and support records where relevant. Identify who can authorise its use, who supervises the activity and what the provider can verify about customer-controlled systems.
For teams handling US healthcare work across shifts, an incident handover should preserve facts without distributing patient information unnecessarily. Define the designated contact, approved reporting route and information needed for the customer's assessment.
Treat Philippine privacy obligations as a separate workstream with its own role and applicability decisions. The same control evidence may help both programmes, but it should not be described as a universal finding of legal compliance.
Agree the assessment outputs with operations, IT, privacy and account owners.
Record customer systems, provider tools, staff access and external parties. Identify unresolved role or contractual questions.
Examine relevant ePHI risks and operating practices. Explain the evidence reviewed, gaps and limits of the assessment.
Assign remediation for access, handling, workspace practices and escalation. Define completion evidence that can be checked during normal supervision.
Use realistic staff scenarios, document results and track corrective action. Establish who keeps instructions and evidence current after the project.
Review an account transfer or end-of-shift escalation. Ask staff to show how access, information and unresolved issues are handed over. Differences between written instructions and actual work should become concrete actions.
Agree technical remediation, client confirmations and specialist legal questions separately. The delivery plan should explain the provider's retained responsibilities rather than relying on the customer's general statement of compliance.
Hypothetical examples, not client case studies or claims of completed engagements.
A hypothetical Manila provider supports a US healthcare scheduling service. Supervisors use call samples to review quality. The assessment identifies the information in those samples, who can access them and how retention decisions are made.
The implementation plan defines approved review methods and controls for copies. Staff receive clear instructions for requests to export or share a recording outside the normal workflow.
A hypothetical Cebu team needs an alternative workspace for a customer service. The change affects devices, connectivity, supervision and the visibility of information on screens.
The provider tests representative work and obtains required customer decisions before proceeding. The evidence records actual safeguards and unresolved limits, rather than assuming the new location is equivalent.
HHS does not recognise private Security Rule certifications. Our scoped assessment supports decisions and remediation; it does not constitute government approval, legal advice on every issue or a guaranteed regulatory conclusion.
No automatic conclusion follows. Establish covered-entity, business-associate or subcontractor status for the actual relationship and activities.
How they approve work, handle exceptions, escalate concerns and retain relevant records. The evidence should reflect the real account instructions.
No. Translate the applicable agreement and requirements into operating actions, technical protections and evidence.
Yes, when included in scope. Review the actual devices, workspace, access, information handling and supervision rather than assuming a standard setup.
No. Agree any separate privacy analysis explicitly and preserve its own applicability and role decisions.
Describe the service, customer boundary, work locations and current concerns. Do not include patient records, recordings or credentials in the enquiry.
HHS: Covered Entities and Business Associates; HHS: Business Associates; HHS: Guidance on Risk Analysis; HHS: Security Rule certification FAQ.
Official references checked 13 October 2026. The implementation examples are practical recommendations; legal applicability and the agreed assurance scope need their own review.
Share the service model and the responsibilities you need to clarify. We can plan assessment and implementation around the actual work, people and information involved.