Business associate agreementRequired before your members’ records can be held here. Scroll to the end to accept.
# Business Associate Agreement
This Business Associate Agreement (the "BAA") is entered into as of the date it is
accepted electronically, by and between **Vince Systems LLC** (formerly Insta Perf LLC),
an Iowa limited liability company, operating the ProveTrip service ("Business
Associate"), and the organization accepting this BAA ("Covered Entity"), in accordance
with the meaning given to those terms at 45 CFR § 160.103.
In this BAA, Covered Entity and Business Associate are each a "Party" and, collectively,
are the "Parties".
## Background
1. Covered Entity is either a "covered entity" or a "business associate" of a covered
entity as each is defined under the Health Insurance Portability and Accountability
Act of 1996, Public Law 104-191, as amended by the HITECH Act and the related
regulations promulgated by HHS (collectively, "HIPAA"), and as such is required to
comply with HIPAA's provisions regarding the confidentiality and privacy of Protected
Health Information.
2. The Parties have entered into or will enter into one or more agreements under which
Business Associate provides or will provide specified services to Covered Entity
(collectively, the "Agreement"), being the provision of the ProveTrip software service
for recording non-emergency medical transport trips and reconciling payment for them.
3. In providing services pursuant to the Agreement, Business Associate will have access
to Protected Health Information.
4. By providing the services pursuant to the Agreement, Business Associate will become a
"business associate" of Covered Entity as that term is defined under HIPAA. Where
Covered Entity is itself a business associate of another entity, Business Associate is
a subcontractor as described at 45 CFR § 164.502(e)(1)(ii), and the obligations of
Business Associate under this BAA are intended to be at least as protective as those
Covered Entity owes upstream.
5. Both Parties are committed to complying with all federal and state laws governing the
confidentiality and privacy of health information.
## 1. Definitions
Capitalized terms used but not defined in this BAA have the meaning given to them by
HIPAA. For clarity:
- **"Breach"** has the meaning given at 45 CFR § 164.402.
- **"Designated Record Set"** has the meaning given at 45 CFR § 164.501.
- **"Electronic Protected Health Information" ("ePHI")** has the meaning given at
45 CFR § 160.103, limited to information created, received, maintained or transmitted
by Business Associate on behalf of Covered Entity.
- **"HITECH Act"** means the Health Information Technology for Economic and Clinical
Health Act, Public Law 111-005.
- **"Individual"** has the meaning given at 45 CFR § 160.103 and includes a person who
qualifies as a personal representative under 45 CFR § 164.502(g).
- **"Protected Health Information" ("PHI")** has the meaning given at 45 CFR § 160.103,
limited to information created, received, maintained or transmitted by Business
Associate on behalf of Covered Entity.
- **"Required By Law"** has the meaning given at 45 CFR § 164.103.
- **"Security Incident"** has the meaning given at 45 CFR § 164.304.
- **"Unsecured PHI"** has the meaning given at 45 CFR § 164.402.
- **"Workforce"** means employees, contractors, agents and other persons whose conduct in
the performance of work for Business Associate is under its direct control, whether or
not paid by Business Associate, consistent with 45 CFR § 160.103.
## 2. Use and Disclosure of PHI
Business Associate may use and disclose PHI only as follows:
(a) as necessary to perform the services described in the Agreement;
(b) as Required By Law;
(c) for the proper management and administration of Business Associate, or to carry out
its legal responsibilities, provided that any disclosure for such purposes is either
Required By Law or made only where Business Associate obtains reasonable assurances from
the person to whom the PHI is disclosed that it will be held confidentially and used or
further disclosed only as Required By Law or for the purpose for which it was disclosed,
and that the person will notify Business Associate of any instance of which it is aware
in which the confidentiality of the information has been breached; and
(d) to provide data aggregation services relating to the health care operations of
Covered Entity, as permitted by 45 CFR § 164.504(e)(2)(i)(B).
Business Associate will not use or disclose PHI in any manner that would constitute a
violation of HIPAA if so used or disclosed by Covered Entity, and will not sell PHI or
use or disclose PHI for marketing or fundraising purposes.
**Business Associate will not use or disclose PHI to train, fine-tune or otherwise improve
any machine learning model.**
**One feature sends a limited amount of PHI to a machine learning model, and it is set out
here rather than left to be discovered.** Covered Entity's dispatchers may send ProveTrip a
message in ordinary words — "move the 9:30 off Dave to Maria" — and a model resolves which
trip, driver and vehicle is meant. For that purpose the model is given an Individual's
surname and the time of the trip, because that is how a dispatcher refers to a run and
often the only way a message can be matched to a record. It is given nothing else about any
Individual: no address, no member identifier, no date of birth, no telephone number, no
diagnosis and no destination. The model resolves names and times only — it performs no
calculation, selects no driver, and decides nothing about whether an action is permitted;
its output is a proposal, a person confirms it, and the same checks that govern the same
action taken through the web interface are applied before anything changes.
That model is Amazon Bedrock, which is part of the Amazon Web Services environment covered
by the executed AWS Business Associate Addendum referred to in section 7, and which does
not use the text sent to it to train any model. Business Associate will not send PHI to any
machine learning or artificial intelligence service outside that environment.
Business Associate will make reasonable efforts to use, disclose and request only the
minimum necessary PHI to accomplish the intended purpose, consistent with
45 CFR § 164.502(b). Any use of PHI by a member of Business Associate's Workforce, and any
disclosure of PHI to a member of its Workforce or to a third party, is limited to the
minimum amount of PHI necessary to achieve the purpose of that use or disclosure.
Except as permitted by this BAA or the Agreement, Business Associate will not disclose PHI
to any third party without the prior written approval of Covered Entity and without first
obtaining that third party's written agreement to be bound by restrictions and conditions
at least as protective as those in this BAA.
## 3. Safeguards Against Misuse of PHI
Business Associate will use appropriate administrative, physical and technical safeguards
to prevent the use or disclosure of PHI other than as permitted by this BAA, and will
comply with the Security Rule at 45 CFR Part 164, Subpart C, with respect to ePHI,
including the standards at 45 CFR §§ 164.308, 164.310, 164.312 and 164.316.
Without limiting the foregoing, Business Associate:
(a) isolates each Covered Entity's records from every other customer's records, and
enforces that isolation in the database itself rather than by application logic alone;
(b) restricts access to PHI to those of its Workforce who require it, and does not
provide its own administrative staff with any means of reading a Covered Entity's member
records through its administrative console;
(c) records access to member records in an append-only audit log available to Covered
Entity;
(d) encrypts PHI in transit and at rest; and
(e) before granting any member of its Workforce access to PHI, informs that person of the
obligations in this BAA and of the consequences of violating them, and binds them in
writing to confidentiality obligations no less protective than those in this BAA.
Business Associate maintains sanctions for members of its Workforce who use or disclose
PHI in violation of this BAA, and will apply them.
## 4. Reporting Disclosures of PHI and Security Incidents
Business Associate will report to Covered Entity any use or disclosure of PHI not
permitted by this BAA, and any Security Incident involving actual unauthorized access to,
use, disclosure, modification or destruction of PHI, without unreasonable delay and in any
event within twenty-four (24) hours of becoming aware of it.
The Parties acknowledge that this section constitutes notice of the ongoing existence and
occurrence of attempted but unsuccessful Security Incidents — such as pings and other
broadcast attacks on a firewall, port scans, unsuccessful log-on attempts, and denial of
service attacks — for which no additional notice will be required.
## 5. Reporting Breaches of Unsecured PHI
Business Associate will notify Covered Entity of any Breach of Unsecured PHI without
unreasonable delay and in no case later than twenty-four (24) hours after discovery of the
Breach. A Breach is treated as discovered on the first day on which it is known, or by
exercising reasonable diligence would have been known, to Business Associate.
Business Associate will give that notice within the time stated even where the facts are
still incomplete, identifying what is then known, and will supplement it as further
information becomes available rather than delaying the first notice until the picture is
settled. The notification will include, to the extent known at the time and supplemented
as further information becomes available:
(a) the identification of each Individual whose Unsecured PHI has been, or is reasonably
believed to have been, accessed, acquired, used or disclosed;
(b) a description of what happened, including the date of the Breach and the date of its
discovery;
(c) a description of the types of Unsecured PHI involved;
(d) a description of what Business Associate is doing to investigate, to mitigate harm,
and to protect against further breaches; and
(e) a contact at Business Associate able to answer questions.
Business Associate will cooperate with Covered Entity in meeting Covered Entity's
obligations under 45 CFR §§ 164.404 through 164.410, and in meeting any corresponding
obligation Covered Entity owes to a health plan, broker or other entity on whose behalf
Covered Entity holds the PHI.
The time limits in this section and in section 4 are set deliberately short. Covered Entity
is commonly required to report a breach to a transportation broker or health plan within
twenty-four hours of learning of it, and a notice from Business Associate that arrived
later than that would put Covered Entity in default of its own obligations.
## 6. Mitigation of Disclosures of PHI
Business Associate will establish and maintain procedures for mitigating, and will
mitigate to the extent practicable, any harmful effect known to it of a use or disclosure
of PHI by Business Associate in violation of this BAA.
## 7. Agreements with Agents or Subcontractors
Business Associate will ensure that any subcontractor that creates, receives, maintains or
transmits PHI on behalf of Business Associate agrees in writing to restrictions and
conditions at least as protective as those that apply to Business Associate under this
BAA, as required by 45 CFR § 164.502(e)(1)(ii) and § 164.308(b)(2). Business Associate
remains responsible to Covered Entity for its subcontractors' performance of those
obligations.
Business Associate's hosting infrastructure is provided by Amazon Web Services under an
executed AWS Business Associate Addendum. Business Associate will make available to
Covered Entity, on request, a current list of the subcontractors that create, receive,
maintain or transmit PHI on its behalf, and will not add one without having the written
agreement described above in place first.
Business Associate does not transmit PHI by text message or by electronic mail. Messages
sent to a Covered Entity's drivers state only the number of trips assigned and their
scheduled times; they name no Individual and contain no information about any
Individual's condition, treatment or destination.
## 8. Security Documentation and Audit
Upon written request, Business Associate will provide Covered Entity with a summary of its
then-current information security practices relevant to the services, and will reasonably
cooperate with Covered Entity's inquiries regarding Business Associate's compliance with
this BAA.
In addition, on reasonable written notice and no more than once in any twelve-month period
unless a Breach or a regulatory inquiry gives cause, Business Associate will make
available for Covered Entity's review its policies and its records relating to the use and
disclosure of PHI, and evidence of the operation of the security controls described in
section 3. Business Associate will produce that evidence from the running system rather
than by assertion, and will assist Covered Entity reasonably throughout.
**Covered Entity may exercise this right on behalf of a payer, broker or other entity to
which it owes an equivalent obligation**, and may bring that entity's representatives,
outside auditors or regulators with it. Covered Entity is commonly required to let such an
entity inspect the records and security controls of everyone handling its PHI, including
Covered Entity's subcontractors; a right exercisable only by Covered Entity itself would
leave it unable to satisfy that, through no fault of its own.
**How the right is satisfied, so that the burden is bounded and the answer is fast.**
Business Associate maintains a dated evidence pack, produced from the running system, that
answers the matters in this section and in section 3. Delivering it satisfies a request
under this section. Where Covered Entity, or an entity on whose behalf it acts, needs
something the pack does not answer, Business Associate will provide it within thirty (30)
days at a time the Parties agree, and may recover its reasonable cost for a second or
further request in any twelve-month period, or for work prepared specifically for one
requester. Nothing in this paragraph lets Business Associate refuse the right; it fixes
what fulfilling it looks like, because an unbounded obligation on a small company is one
that gets met late or not at all.
Three limits are stated plainly rather than left to be discovered. First, Business
Associate cannot grant access to the facilities in which the service is hosted, because
they are operated by Amazon Web Services; for those controls Business Associate will
provide the current third-party audit reports it is permitted to share. Second, nothing
produced under this section will include another customer's PHI, and where a record cannot
be separated Business Associate will provide it in redacted form and say what was withheld
and why. Third, this section is a right to inspect records, policies and evidence of
controls — it is not a right to direct Business Associate's engineering, to require a
specific certification, or to test the service against Covered Entity's own standard.
## 9. Access to PHI by Individuals
Business Associate will, within ten (10) business days after written request by Covered
Entity, make available to Covered Entity PHI in a Designated Record Set held by Business
Associate as necessary for Covered Entity to satisfy its obligations under
45 CFR § 164.524. Where an Individual makes such a request directly to Business Associate,
Business Associate will notify Covered Entity and forward the request promptly, and in no
event later than one (1) business day after receiving it, and Covered Entity is responsible
for responding. The window is one day because Covered Entity may owe an upstream payer or
broker notice of such a request immediately on receiving it, and a request held here is a
delay Covered Entity would have to account for.
## 10. Amendment of PHI
Business Associate will, within ten (10) business days after written request by Covered
Entity, make available PHI in a Designated Record Set for amendment, and incorporate any
amendment to that PHI, as necessary for Covered Entity to satisfy its obligations under
45 CFR § 164.526. Where an Individual makes a request to amend PHI directly to Business
Associate, Business Associate will notify Covered Entity and forward the request promptly,
and in no event later than one (1) business day after receiving it, for the same reason as
in section 9, and will make no amendment except as Covered Entity directs or authorizes.
## 11. Accounting of Disclosures
Business Associate will document each disclosure of PHI made for a reason other than
performing the services, and information related to those disclosures, as would be
required for Covered Entity to respond to a request for an accounting of disclosures under
45 CFR § 164.528, and will, within ten (10) business days after written request by Covered
Entity, make that information available to Covered Entity.
For each such disclosure the record will state:
(a) the date of the disclosure;
(b) the name and, if known, the address of the recipient of the PHI;
(c) a copy of the request for the disclosure, if any, together with any consent or
authorization relied on;
(d) a brief description of the PHI disclosed; and
(e) a statement of the purpose of the disclosure, in terms that would reasonably inform
the Individual of it.
## 12. Availability of Books and Records
Business Associate will make its internal practices, books and records relating to the
use and disclosure of PHI available to the Secretary of the U.S. Department of Health and
Human Services for purposes of determining Covered Entity's compliance with HIPAA, and
will notify Covered Entity of any such request unless prohibited from doing so by law.
## 13. Responsibilities of Covered Entity
Covered Entity will:
(a) promptly notify Business Associate of any limitation in its notice of privacy
practices, of any changes in or revocation of an Individual's permission to use or
disclose PHI, and of any restriction on the use or disclosure of PHI that Covered Entity
has agreed to or is required to abide by under 45 CFR § 164.522, in each case to the
extent it affects Business Associate's use or disclosure of PHI;
(b) not request Business Associate to use or disclose PHI in any manner that would not be
permissible under HIPAA if done by Covered Entity;
(c) be solely responsible for the accuracy and lawfulness of the PHI it, or those acting
on its behalf, enters into the service, and for managing which of its own workforce have
access to it; and
(d) promptly notify Business Associate where an Individual asks that PHI held in the
service be made available to them or amended, and of any request Covered Entity receives
that requires Business Associate to act under sections 9, 10 or 11; and
(e) keep the credentials issued to its workforce secure, give each person their own and
not share or resell an account, and promptly notify Business Associate where a credential
is lost or compromised or where a person with access leaves Covered Entity. Business
Associate records which account did what, so a shared login makes Covered Entity's own
audit log unable to answer who read a member's record — which is the question the log
exists to answer; and
(f) **be responsible for what its own workforce does with PHI the service shows them.**
Covered Entity's drivers, dispatchers and office staff are its workforce, not Business
Associate's. Covered Entity will inform them of their obligations before giving them
access, train them, and apply sanctions where one of them uses or discloses PHI
improperly, as 45 CFR §§ 164.308(a)(5) and 164.530(b) and (e) require of it — the same
obligations Business Associate carries for its own workforce under section 3.
**Where the line falls, stated plainly because this is the most common way PHI escapes in
this industry.** What the service puts in front of a person is Business Associate's
responsibility, and it is limited to what the trip cannot be performed without: who is
being collected and when, the service level and any mobility, oxygen, service-animal or
language need, the pickup and dropoff addresses and any stop between them, and a telephone
number to reach the Individual on the day. Business Associate applies the minimum
necessary standard in section 2 to that screen, and does not itself place a diagnosis, a
member identifier or a payer record on it. A free-text mobility note is written by Covered
Entity's own staff, so what goes into it is Covered Entity's choice under paragraph (f).
What the person then does with what they were shown — a name read aloud in a waiting room,
a manifest left on a seat, a screenshot sent to somebody — is Covered Entity's
responsibility, because that person answers to Covered Entity and not to Business
Associate. Business Associate cannot see it, cannot prevent it, and will not learn of it
unless Covered Entity says so. That is also why the reporting duties in sections 4 and 5
run on what Business Associate discovers: a disclosure that happens outside the service is
Covered Entity's to find and to report.
## 14. Data Ownership
As between the Parties, all PHI and all records created in the service on behalf of
Covered Entity remain the property of Covered Entity. Business Associate acquires no
ownership interest in them and no right to use them other than as set out in this BAA and
the Agreement.
Covered Entity may export its records at any time while its account is open.
## 15. Term and Termination
This BAA takes effect on the date it is accepted or, if earlier, the date Business Associate
first receives PHI from or on behalf of Covered Entity. It continues until the Agreement
ends or it is terminated as provided below, and in any event until all PHI held by Business
Associate on behalf of Covered Entity has been returned or destroyed.
Covered Entity may terminate this BAA and the Agreement if Business Associate materially
breaches this BAA and fails to cure the breach within thirty (30) days of written notice,
or immediately if cure is not possible.
**Business Associate has the same right, and in some circumstances a duty.** Business
Associate may terminate this BAA and the Agreement if Covered Entity materially breaches
this BAA and fails to cure within thirty (30) days of written notice, or immediately if
cure is not possible. Where Business Associate becomes aware of a pattern of activity or
practice of Covered Entity that constitutes a material breach of this BAA, it will take
reasonable steps to have it cured and, if that fails, will terminate or report the problem
as HIPAA requires. Before terminating, Business Associate will restrict or suspend the
narrower thing where that would end the problem, because this service dispatches transport
people need on the day; sections 7 and 9 of the Agreement govern suspension and what
happens to Covered Entity's records.
Upon termination, Business Associate will, if feasible, return or destroy all PHI it
maintains on behalf of Covered Entity and retain no copies. Where return or destruction is
not feasible, Business Associate will extend the protections of this BAA to that PHI and
limit further use and disclosure to those purposes that make return or destruction
infeasible, for so long as it is retained. Business Associate will tell Covered Entity
which PHI it is retaining and why, and if return or destruction later becomes feasible it
will notify Covered Entity and act on Covered Entity's instruction to return or destroy
it.
Covered Entity may request an export of its records for a period of thirty (30) days after
termination.
The obligations of Business Associate under this section survive termination.
## 16. Effect of BAA
To the extent this BAA conflicts with any other term of the Agreement in respect of PHI,
this BAA controls. In all other respects the Agreement remains in effect.
**The limitation of liability in the Agreement applies to this BAA.** The cap and the
exclusion of indirect loss set out in the Subscription and Payment Terms govern every claim
arising under this BAA, including a claim relating to PHI, except where a limitation is
prohibited by law. Nothing in the paragraph above displaces them: this BAA controls what
the Parties must do with PHI, and the Agreement controls what either Party can be made to
pay. Where Covered Entity has not accepted those Terms, Business Associate's aggregate
liability under this BAA is limited to the fees Covered Entity paid for the service in the
twelve months before the event first giving rise to the claim.
**Each Party answers for its own breach, and not the other's.** Business Associate is
responsible for a Breach, or an impermissible use or disclosure of PHI, caused by its own
act or omission, or by that of its workforce or of a subcontractor it engaged. Covered
Entity is responsible for one caused by its own act or omission, or by that of its
workforce — including the conduct described in section 13(f) — or by a person who obtained
access through Covered Entity's credentials other than through a failure of the service.
Where both contributed, each bears the share attributable to it. Nothing in this BAA makes
either Party liable for the other's acts, and the limitation referred to above applies on
top of that allocation rather than in place of it.
Any ambiguity in this BAA will be resolved in favour of a meaning that permits the Parties
to comply with HIPAA.
## 17. Regulatory References
A reference in this BAA to a section of HIPAA means that section as in effect or as
amended, and for which compliance is required.
## 18. Notices
Notices to Business Associate go to:
> Vince Systems LLC
> 3930 Westwind Ct, Waukee, IA 50263
> vince@vincesystems.com
Notices to Covered Entity go to the address and email held on its account, which Covered
Entity is responsible for keeping current.
A notice required within twenty-four hours under section 4 or section 5 may be given by
electronic mail to that address, and will be followed by written notice.
**When a notice counts as given.** An electronic mail notice is given when it is sent to
the address held on the account, whether or not it is opened; a notice sent by overnight
carrier or certified mail is given on delivery. This matters because of the twenty-four
hour windows in sections 4 and 5: without it, a Party could argue the clock had not started
until somebody read the message, which is the opposite of what those sections are for. Each
Party is responsible for keeping an address on file that somebody reads.
## 19. Amendments and Waiver
This BAA may not be amended except in writing. The Parties agree to take such action as
is necessary to amend this BAA from time to time as is necessary for the Parties to comply
with HIPAA.
No failure or delay in exercising a right under this BAA operates as a waiver of it.
## 20. HITECH Act Compliance
Business Associate acknowledges that it is directly subject to those provisions of the
HITECH Act and the HIPAA Security and Privacy Rules that apply to business associates,
and agrees to comply with them.
## 21. Workforce and Personnel Changes
Business Associate will notify Covered Entity within fifteen (15) days where a member of
its Workforce who held access to PHI, to credentials issued by Covered Entity, or to any
system of Covered Entity, ceases to hold that access or leaves Business Associate, and
will revoke that access promptly rather than on notice.
On request, Business Associate will identify the members of its Workforce who are able to
access PHI held on behalf of Covered Entity.
## 22. Carrying Out Covered Entity's Obligations
To the extent Business Associate is to carry out any obligation of Covered Entity under
Subpart E of 45 CFR Part 164, Business Associate will comply with the requirements of that
Subpart that apply to Covered Entity in the performance of that obligation.
## 23. No Third-Party Beneficiaries
Nothing in this BAA confers any right, benefit or cause of action, in contract or
otherwise, on any person who is not a Party, including any Individual whose PHI is used or
disclosed under it or any personal representative of such a person.
## 24. Severability
If any provision of this BAA is held invalid or unenforceable, that provision is severed
and the rest of this BAA remains in force, and the severed provision is treated as replaced
by one that is enforceable and comes closest to what the Parties intended.
This matters most for the limitation of liability referred to in section 16. If a court
declines to enforce that limitation, the rest of this BAA stands rather than failing with
it, and the limitation is reduced to the greatest extent the court will allow instead of
disappearing.
---
This agreement is governed by the laws of the State of Iowa.
Accepted electronically by the person named at acceptance, on behalf of Covered Entity,
who represents that they are authorised to bind it. The version accepted, the full text
shown, a SHA-256 hash of that text, the acceptor's name, title and email, the IP address
and the time of acceptance are recorded by Business Associate.