Framing: determine each party’s role and permitted use of data before prescribing a standard agreement. HHS explains that disclosures between healthcare providers for treatment do not automatically require a business associate agreement. Business-associate requirements must be assessed for the actual functions involved. (hhs.gov)
Put to: Jesse Dresser and Rae McMahan, with a healthcare privacy and security specialist.
Buyer owner: Compliance lead, technology lead and COO.
Why it matters: The buyer needs sufficient visibility to manage access while avoiding an indiscriminate demand for patient information or an assumption that one contract covers every use.
A good answer should cover:
- The pharmacy, platform and clinic’s respective covered-entity or business-associate roles where applicable.
- Permitted treatment, payment, operations and other uses, assessed separately.
- The minimum operational event set needed for support and reporting.
- Patient communications, marketing permissions, subcontractors and incident responsibilities.
- Data export, retention, access termination and continuity during migration.
Follow-up that tests the answer: “If the routing platform disappears, can we identify unresolved prescriptions and continue supporting patients without recreating the entire order history?”
Evidence to request: A reviewed data-flow diagram, field dictionary, security evidence and export test. Use synthetic or appropriately de-identified information for procurement demonstrations rather than collecting patient records in the research desk.
Expert quote — reserved: ________________________________________
Sources cited on this page
- hhs.gov · Source 1 ↗https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/business-associates/index.html?utm_source=openai