HL7 v2 Interface Agreement
Signed by a laboratory, imaging center, hospital or HIE before it sends HL7 v2 results or hospital notices into a practice on ChartVoyant. Covers the treatment purpose, transport and credential security, testing first, breach notice and a twelve-month term.
- 1 · Your email
- 2 · Verify
- 3 · Complete & sign
- 4 · Done
Start signing
We email you a six-digit code to confirm the address, then you complete and sign the agreement. It takes a few minutes.
The executed copy is sent here. Use an address you can open right now.
The sender
These answers are printed on the Execution Schedule of the signed agreement.
The interface
One interface delivers into one practice. Send no patient data anywhere on this form.
The practice on ChartVoyant whose patients the messages are about.
ChartVoyant accepts ORU^R01 and the ADT events listed on chartvoyant.com/developers/hl7.
Either way the credential is bound to this one interface and can do nothing else (§6).
§4(b): you are responsible for it, including any business associate agreement HIPAA requires with it.
Contacts
Expiry, incident and change notices go to these addresses (§10 and §11).
Where ChartVoyant sends a security incident notice.
Who is signing
As it should appear on the agreement.
The agreement
CV-IFA-001 · version 1.0. This is the text you are signing; the copy we email you contains it in full, with your answers and a certificate of completion.
| Document control | |
|---|---|
| Document ID | CV-IFA-001 |
| Version | 1.0 |
| Effective date | (per executed copy) |
| Owner | Security Official (see CV-DES-001) |
| Review cycle | Annually, and whenever the HL7 v2 interface changes in a way the Documentation records |
| Retention | 6 years from the date the agreement ends |
| Legal entity | Geach Technologies, LLC ("ChartVoyant"), trading as ChartVoyant |
Companion documents: CV-API-001 API Use Agreement (every other kind of API access) · CV-BAA-002 and CV-BAA-003 business associate agreements · the HL7 v2 documentation at chartvoyant.com/developers/hl7
1. Parties and background
This HL7 v2 Interface Agreement ("Agreement") is entered into between Geach Technologies, LLC, trading as ChartVoyant ("ChartVoyant"), and the organization named as the Sender on the Execution Schedule ("Sender").
ChartVoyant provides an electronic health record to the medical practice named on the Execution Schedule (the "Practice") and receives and stores the Practice's information as its business associate. Sender — a laboratory, imaging center, hospital, health system, health information exchange or other organization — wishes to deliver HL7 version 2 messages about the Practice's patients, such as results and admission, discharge and registration notices, into the Practice's ChartVoyant record. This Agreement sets the terms on which ChartVoyant operates that connection (the "Interface") and Sender uses it.
2. Definitions
- "Credential" means the HL7 sender key or the SMART Backend Services client that ChartVoyant binds to the Interface, and any secret or private key behind it.
- "Documentation" means ChartVoyant's HL7 v2 documentation published at chartvoyant.com/developers/hl7, as updated from time to time.
- "Go-Live" means the date ChartVoyant confirms to Sender's technical contact, in writing, that the Interface is turned on for Messages about real patients.
- "Interface" means the one HL7 v2 receiving endpoint ChartVoyant sets up for Sender and the Practice, identified by its interface ID.
- "Messages" means the HL7 v2 messages Sender sends through the Interface.
- "PHI" means protected health information as defined at 45 CFR §160.103.
- "Synthetic Messages" means messages that describe only fictitious people and contain no information about any real individual.
3. Purpose and scope
(a) Treatment. The Interface exists so that information Sender holds about the Practice's patients reaches the Practice for treatment and the Practice's health care operations. A covered entity may disclose protected health information to a health care provider for that provider's treatment of an individual under 45 CFR §164.506(c)(2), and ChartVoyant receives Messages on the Practice's behalf.
(b) One interface, one practice. This Agreement covers one Interface delivering into one Practice, for the message types on the Execution Schedule. Another practice, another feed or another message type needs its own setup and may need its own agreement.
(c) Inbound only. ChartVoyant returns HL7 acknowledgments, which carry no patient information. Nothing in this Agreement sends any other information from ChartVoyant or the Practice to Sender.
(d) The Practice's request. ChartVoyant sets up and operates the Interface only at the Practice's request. The Practice may stop it at any time.
4. Relationship to HIPAA and other agreements
(a) Not a business associate agreement. Where HIPAA requires one — for example, where Sender acts on behalf of the Practice rather than as a provider disclosing for treatment — the parties concerned will execute it separately before any PHI is sent.
(b) Intermediaries. If an interface engine, health information exchange, VPN or network provider carries Messages for Sender, Sender names it on the Execution Schedule, is responsible for it, and is responsible for having in place any business associate agreement HIPAA requires with it. ChartVoyant may ask for a copy before Go-Live.
(c) Each party's own compliance. Each party remains responsible for its own compliance with the HIPAA Rules, Tennessee law and any other law that applies to it, including its own breach notification duties.
(d) Other agreements. This Agreement does not change any agreement between Sender and the Practice, and does not make ChartVoyant a party to one.
5. Testing comes first
(a) Before Go-Live, the Interface and any test interface ChartVoyant provides accept Synthetic Messages only, with processing ID T.
(b) Sender will not send a Message about a real person before Go-Live. If it does, Sender notifies ChartVoyant under §10 within one (1) business day, and ChartVoyant may delete the message from any test environment and suspend the Interface.
(c) Go-Live happens only when ChartVoyant has the approvals the Documentation describes on file — including this Agreement, independent security testing of the Interface and the Practice's go-ahead — and confirms Go-Live in writing. ChartVoyant decides when those conditions are met.
6. Transport and the Credential
(a) HTTPS only. Sender sends Messages only to the endpoint in the Documentation, over HTTPS with TLS 1.2 or later, one Message per request, within the size and rate limits stated there. MLLP, SFTP and other transports are not offered under this Agreement.
(b) One Credential, one Interface. ChartVoyant binds one Credential to the Interface. It authorizes delivering Messages to that Interface and nothing else. Sender will not use it for any other purpose or share it with another organization.
(c) Custody. Sender keeps the Credential on servers it controls, in a secrets manager or an equivalent encrypted store. Sender will not put it in source control, a container image, a log, a ticket, an email, a chat, or an AI assistant's conversation, and will limit access to the personnel who operate the Interface.
(d) Rotation and exposure. Sender asks for a replacement before the Credential expires and whenever someone with access to it leaves. Sender reports any actual or suspected exposure of the Credential under §10 within twenty-four (24) hours, and ChartVoyant may revoke it at once.
(e) Security. Sender maintains administrative, physical and technical safeguards for the systems that create and send Messages that are appropriate to the sensitivity of the information, and at least those the HIPAA Security Rule requires of Sender where it applies.
7. Message content
(a) Accuracy. Sender is responsible for the content of each Message: that it is about the patient it identifies, that it is complete and accurate, and that it goes to the right Interface. ChartVoyant files Messages as received and does not verify their clinical content.
(b) Identifiers and conformance. Sender sends the message types, HL7 version, sending application and facility (MSH-3 and MSH-4) and patient identifier assigning authority (PID-3) recorded for the Interface, conforming to the profile the Documentation describes, and tells ChartVoyant in advance of any change to them.
(c) Corrections. Sender corrects a result by sending a corrected Message as the Documentation describes (for example, a C status in OBR-25 or OBX-11), not by asking ChartVoyant to edit the record.
(d) Wrong recipient. Sender sends only Messages about patients of the Practice. A Message sent to the wrong Interface or about the wrong patient is a security incident under §10.
8. Acknowledgments and delivery
(a) What AA means. An HL7 acknowledgment of AA means ChartVoyant has stored the Message durably. It does not mean the Message has been matched to a patient, reviewed by a clinician or acted on. Sender handles AE and AR acknowledgments as the Documentation describes.
(b) Matching. ChartVoyant matches a Message to a patient only as the Documentation describes. A Message it cannot match is held for the Practice's staff. ChartVoyant never creates or merges a patient record from a Message.
(c) No substitute for Sender's own duties. The Interface is not a means of communicating critical, panic or otherwise urgent results. Sender remains responsible for communicating those directly to the ordering clinician by whatever means its own policies, its accreditation and the law require, and for any duty it has to report a result by other means when the Interface is unavailable or a Message is not acknowledged.
9. How ChartVoyant handles Messages
ChartVoyant uses and discloses Messages only to provide its services to the Practice, as its business associate agreement with the Practice permits, and as the law requires. Messages become part of the Practice's records and are retained under the Practice's instructions and the law, including after this Agreement ends. ChartVoyant does not sell Messages.
10. Security incidents
Each party notifies the other's security contact (Sender's is on the Execution Schedule; ChartVoyant's is info@chartvoyant.com) without unreasonable delay, and in any event within five (5) business days of discovery, of any security incident affecting Messages, the Interface or the Credential — and within the shorter times in §5(b) and §6(d) where they apply. The notice includes what is known at the time and is updated as more is learned. Each party cooperates reasonably with the other's investigation. Nothing here changes either party's own notification duties to individuals, regulators or the Practice.
11. Contacts
Each party keeps its technical and security contacts current and answerable. Notices about expiry, incidents and changes to the Interface go to those contacts by email, which is sufficient notice under this Agreement.
12. Changes to the Interface
ChartVoyant may change the Interface, the Documentation, the supported message types and versions, and the limits. ChartVoyant will give Sender's technical contact reasonable advance notice of a change that requires Sender to change what it sends, except where a shorter timeline is needed for security.
13. Suspension, term and termination
(a) Suspension. ChartVoyant may suspend the Interface or revoke the Credential at any time — including where the Practice asks, where there is a security concern, or where Messages do not conform — and the Practice may direct ChartVoyant to do so at any time. Suspension gives rise to no liability of ChartVoyant or the Practice to Sender.
(b) Term. This Agreement starts on the date ChartVoyant countersigns it (the "Effective Date") and ends twelve (12) months later. The parties continue the Interface by executing a new agreement before then; ChartVoyant stops the Interface when the term ends without one.
(c) Termination. Either party may end this Agreement on thirty (30) days' written notice, or immediately on written notice for the other's material breach or a security incident. It ends automatically if the Practice withdraws its request or stops using ChartVoyant.
(d) On ending. ChartVoyant revokes the Credential and stops the Interface. Messages already received remain part of the Practice's records. Sections 4, 7(a), 8(c), 9, 10, 14, 15, 16 and 18 survive.
14. No warranty
The Interface, the endpoint, any test environment and the Documentation are provided "as is" and "as available", without warranty of any kind, express or implied, including merchantability, fitness for a particular purpose, and any warranty that they will be uninterrupted, timely, error-free or secure.
15. Limitation of liability
To the maximum extent permitted by law:
- ChartVoyant is not liable to Sender, or to anyone claiming through Sender, for any indirect, incidental, special, consequential, exemplary or punitive damages, or for any loss of profits, revenue, business, goodwill or data, arising out of or relating to this Agreement or the Interface, under any theory of liability, even if advised of their possibility;
- ChartVoyant's total liability arising out of or relating to this Agreement or the Interface will not exceed one hundred dollars ($100); and
- ChartVoyant has no liability for the content of any Message, for a Message delayed, refused or not delivered, or for any act or omission of Sender, its personnel, its intermediaries or its subcontractors.
These limits apply even if a limited remedy fails of its essential purpose. They do not limit liability for fraud, gross negligence or willful misconduct where applicable law does not allow that liability to be limited.
16. Indemnity
Sender will defend, indemnify and hold harmless ChartVoyant and its members, managers, officers, employees and contractors, and the Practice, from and against any claim, demand, investigation, proceeding, judgment, settlement, loss, damage, cost or expense — including reasonable attorneys' fees and, to the extent permitted by law, fines and penalties — arising out of or relating to:
- the content of any Message, including a Message that is inaccurate, incomplete, about the wrong patient, or sent to the wrong Interface;
- Sender's breach of this Agreement;
- use of the Credential by anyone who obtained it from Sender or from Sender's systems; or
- a security incident involving Messages or the Credential while in the possession or control of Sender, its personnel, its intermediaries or its subcontractors.
ChartVoyant may take part in the defense with counsel of its choice at its own expense. Sender will not settle a claim in a way that imposes any obligation on, or admits fault by, ChartVoyant or the Practice without its prior written consent.
17. Fees and insurance
This Agreement does not itself set any fee; any fee for the Interface is agreed separately in writing. Sender maintains insurance customary for an organization of its kind, including cyber liability coverage, and provides a certificate of insurance on request.
18. General
(a) Confidentiality. Each party protects the other's non-public information disclosed under this Agreement — including the interface ID, the Credential and any non-public Documentation — with at least reasonable care, and uses it only to perform under this Agreement.
(b) The Practice. The Practice is an intended third-party beneficiary of Sender's obligations under this Agreement. No other person is.
(c) Assignment. Sender may not assign this Agreement or transfer the Credential, including by merger or change of control, without ChartVoyant's prior written consent.
(d) Governing law. This Agreement is governed by the laws of the State of Tennessee, without regard to its conflict-of-laws rules. The parties consent to the exclusive jurisdiction of the state and federal courts located in Hamilton County, Tennessee.
(e) Entire agreement. This Agreement, including the Execution Schedule, is the entire agreement between the parties on its subject. Amendments must be in writing and signed by both parties. If any provision is held unenforceable, the rest remains in effect.
(f) Counterparts and electronic signatures. This Agreement may be executed in counterparts and electronically, and an electronic signature has the same effect as an original.
19. Signatures
| ChartVoyant | Sender | |
|---|---|---|
| Entity | Geach Technologies, LLC | ______ |
| Signed | ______ | ______ |
| Name | ______ | ______ |
| Title | ______ | ______ |
| Date | __ | __ |
20. Document history
| Date | Version | Change |
|---|---|---|
| 2026-11-01 | 1.0 | Issued, signable online at e-sign.chartvoyant.com/hl7interfaceagreement. Covers what the interop design and the HL7 v2 developer page require of an interface agreement — the treatment purpose, transport and credential security, breach notice, contacts and termination — plus testing before go-live, message content, acknowledgments, a twelve-month term and the same risk allocation as CV-API-001. Not yet reviewed by outside counsel. |
Confirm and sign
Typing your name here is your signature. It has the same legal effect as signing on paper.
Signing records your name, the time, your IP address and browser on a certificate of completion bound into the signed PDF.