
Master Services Agreement | Schedule A | Schedule B | Schedule C Publication version: 1.0 — November 2026
This Services Agreement (the “Agreement”) is effective as of the Effective Date indicated on your Order Form. DayaMed and Customer are referred to herein individually as “Party” and collectively as the “Parties.” The Agreement includes the applicable Order Form and Schedules A, B, and C.
The Parties hereby agree as follows:
“Authorized User(s)” means Customer, its employees and contractors, and the licensed healthcare professionals Customer authorizes to use the Platform.
“Business Associate Agreement” or “BAA” means the agreement incorporated as Schedule B governing the Parties’ use and disclosure of Protected Health Information and other applicable HIPAA obligations.
“Customer Data” means (a) all data and information Customer submits or transmits to DayaMed; and (b) data, records, and information DayaMed generates that relates directly to the Services under this Agreement. Customer Data does not include (i) information or documentation that DayaMed generates for use in DayaMed’s business generally or for use with multiple customers; (ii) PHI (as defined below), as PHI is governed by the BAA between the parties; or (iii) De-Identified Data.
“Customer Support” means the technical support services that DayaMed provides to Customer to support Customer’s use of the Platform.
“DayaMed Data” means: (a) all data, software (in any form), and information DayaMed submits or transmits to Customer regarding DayaMed; (b) all data, records, and information generated in DayaMed’s business or operations, including any information relating to DayaMed’s subcontractors and/or affiliates; (c) all DayaMed Intellectual Property (defined below), together with all derivative works of the DayaMed Intellectual Property; and (d) data, records, or information occurring in any form, including written, graphic, electronic, visual, or fixed in any tangible medium of expression and whether developed, generated, stored, possessed, or used by DayaMed, Customer, or a third party if related to the items described in (a) through (c) above. DayaMed Data does not include any data or information that relates exclusively to Customer or Customer’s business, operations, or activities.
“Intellectual Property Rights” means any patent, invention, discovery, know-how, moral, technology, software, copyright, authorship, trade secret, trademark, trade dress, service mark, confidentiality, proprietary, privacy, intellectual property, or similar rights (including rights in trademark applications, registrations, filings, and renewals) that are now or hereafter protected or legally enforceable under state and/or Federal common laws or statutory laws or laws of foreign jurisdictions.
“Order Form” means the form provided to Customer for purposes of selecting the services to be provided under this Agreement.
“Participating Patient(s)” means those patients that Customer determines may benefit from the Services, are enrolled in RPM, RTM, PCM, CCM, and/or BHI services through the Platform, and who have agreed to the Terms of Use.
“Patient Mobile App” means the mobile software application that uses a patient’s smartphone camera to scan a medication barcode to collect and transmit patient medication adherence data to providers. The Patient Mobile App also displays a portion of the data collected to Participating Patients.
“Platform” means the Patient Mobile App and the Provider-Facing Dashboard, all of the capabilities and functionalities associated with the Patient Mobile App and Provider-Facing Dashboard, and user support services provided by DayaMed.
“Protected Health Information” or “PHI” shall have the meaning ascribed to such term in 45 C.F.R. 160.103.
“Provider-Facing Dashboard” means a web-based software platform that allows healthcare providers to view, analyze, and manage their Participating Patients’ medication adherence information and overall care plan.
“Schedule” means the attachment(s) to this Agreement outlining the scope, objectives, and responsibilities of either Party necessary for the delivery of the Services (defined below). Schedule A describes the available Services; Schedule B contains the BAA; and Schedule C establishes the clinical services and supervision framework. Clinical Staff and DayaMed Clinical Staff referenced in this Agreement are DayaMed Clinical Personnel as defined in Schedule C.
“Terms of Use” or “TOU” means the agreement between each Authorized User and DayaMed governing each user’s activities within the Platform.
DayaMed agrees to provide, and Customer agrees to purchase, the administrative access services, remote monitoring services and/or the care management services (the "Services"), as indicated on the Order Form and as more fully described in an applicable Schedule. Clinical Services shall be furnished subject to the service-specific requirements and allocation of responsibilities in Schedule C. Schedule C does not add programs that are not selected in the Order Form and described in Schedule A.
Medical Billing Services. If Customer selects Medical Billing Services on the applicable Order Form, DayaMed shall arrange for such services to be performed by GAPP Healthcare Solutions, LLC or another designated billing services provider. Medical Billing Services may include, as applicable, patient registration support, insurance verification, charge capture, claim preparation, claim submission, coding support (where applicable), payment posting, denial management, accounts receivable follow-up, reporting, and other revenue cycle management services. Unless otherwise stated in the applicable Order Form, these services are included within the Service Fees and do not result in additional charges to Customer. Where Medical Billing Services are selected, the applicable Order Form shall identify the billing entity and the Party responsible for claim submission. Unless another lawful arrangement is expressly agreed in writing, Customer is the billing entity and DayaMed or its designated provider prepares and submits claims on Customer’s behalf. Claims shall use the billing and rendering identifiers required by the applicable payer. Delegated billing does not eliminate Customer’s responsibility for its clinical decisions, practitioner eligibility, or information supplied, or DayaMed’s responsibility for its own services and documentation. The Parties shall cooperate in verifying attribution, correcting identified errors, and preventing duplicate claims. Required payer enrollment, clearinghouse, or billing-authority forms remain subject to the applicable third party’s requirements. Schedule C addresses clinical supervision and operations and does not authorize Medical Billing Services.
Unless otherwise indicated on an Order Form, the term of this Agreement will begin on the Effective Date and continue for thirty six (36) months thereafter (the “Initial Term”). Upon expiration of the Initial Term, the Agreement shall automatically renew for successive twelve (12) month terms (each a “Renewal Term”), unless either Party provides written notice of its desire not to renew within the advance notice period expressly specified in the applicable Order Form or, if no period is specified, no less than sixty (60) days prior to the expiration of the then-current term or otherwise terminates this agreement as provided in Section 8. The Initial Term and each Renewal Term shall collectively constitute the “Term” of this Agreement. Schedule C shares the Effective Date, Term, and termination provisions of this Agreement and has no separate renewal term.
Operations & Enrollment. Customer is responsible for identifying and ordering the Services for Participating Patients and for providing all reasonably requested information to DayaMed to allow DayaMed to furnish its Services to Participating Patients. Eligibility, medical necessity, required orders, and enrollment controls for Clinical Services shall be addressed as provided in Schedule C, Sections 5 and 9.
System. Except for the products and services provided by DayaMed under this Agreement, Customer is responsible for (a) obtaining, deploying, and maintaining all hardware, software, and equipment necessary for Customer and its Authorized Users to access and use the Services; (b) contracting with third-party ISP, telecommunications, and other service providers as necessary to access and use the Services; and (c) paying all third-party fees and access charges incurred in connection with the foregoing. DayaMed will not be responsible for supplying any other hardware, software, or other equipment not specifically addressed in this Agreement and cannot be held responsible for any interruption in the Services that occurs because of any of the foregoing or Customer’s failure to maintain any of the foregoing.
Consents. Unless otherwise agreed in writing, DayaMed will obtain patient consent for the Services in a format approved by Customer. Customer is responsible for obtaining and maintaining all other necessary consents and authorizations to enable DayaMed to use, upload, process, and store Customer Data and to provide the Services to Participating Patients, including without limitation consent to receive phone calls, email, postal mail, and text messages regarding a Participating Patient’s care from DayaMed on behalf of Customer. Customer represents and warrants that it will not furnish any Customer Data that includes an individual’s PHI to DayaMed in the event such individual objects. Customer acknowledges and accepts full responsibility and liability for all Customer Data. Required service consent shall be obtained, verified, and documented before initiating services that require it, in accordance with Schedule C, Section 9.
Supervision. Customer and DayaMed shall fulfill their respective clinical supervision responsibilities in accordance with Schedule C. The required level of supervision shall be determined separately for each selected Service under applicable law, licensing requirements, and payer rules. Customer shall designate qualified Supervising Practitioners and maintain required patient-level attribution. DayaMed may substitute qualified Clinical Personnel and Customer may update practitioner assignments as permitted in Schedule C without separate agreements for each practitioner or staff member.
Patient Care Plan. Customer is responsible for developing, providing, approving, and maintaining each Participating Patient’s care plan as required for the selected Service. DayaMed may assist with care-plan development and documentation within approved protocols and lawful scope as provided in Schedule A and Schedule C, Sections 5 and 6. Customer shall notify DayaMed of relevant care plan changes on an ongoing basis. Practitioner-level treatment decisions remain with Customer and its qualified practitioners.
Clinical Contact. Customer shall identify a Clinical Contact and backup coverage available during Clinical Hours defined in Schedule A to communicate with DayaMed Clinical Personnel and arrange practitioner response when necessary. Contact details, escalation thresholds, expected response times, and after-hours arrangements shall be maintained under Schedule C, Sections 5 and 7. Customer remains responsible for any program-specific after-hours access obligations described in Schedule A.
Unenrollment of Patients. Customer is responsible for determining when Services are no longer medically necessary or a Participating Patient is unable or unwilling to participate, and for promptly notifying DayaMed or unenrolling the patient through the Platform. DayaMed shall notify Customer when persistent nonparticipation is identified so the Parties may discuss continued enrollment or unenrollment. If a patient withdraws consent, DayaMed shall unenroll the patient and notify Customer. Fees shall accrue only as provided in Section 5 for Services actually furnished before unenrollment; enrollment alone does not create a fee obligation. The Parties shall coordinate consent withdrawal, loss of eligibility, and patient transition under Schedule C, Sections 9 and 11. No contractual fee provision authorizes a claim that fails applicable payer requirements.
EHR Access. Before services begin, Customer shall provide secure, individual, role-appropriate access credentials and remote access reasonably necessary for authorized Services. Access, the designated system of record, documentation timing, and authorized record transfer shall comply with Schedule B and Schedule C, Section 8. Personnel shall not share credentials.
Complying with Requests. Customer shall comply with all reasonable requests from DayaMed for information to ensure DayaMed is able to comply with its obligations under this Agreement. DayaMed shall not be responsible for any delay in Services or other negative impact resulting from Customer’s failure to comply with this Section.
Terms of Use. Customer is responsible for its actions and the actions of its Authorized Users while using the Platform. As a condition to Customer’s and its Authorized Users’ use of the Platform, Customer shall require its Authorized Users to review and accept the DayaMed TOU, as updated by DayaMed from time to time, prior to accessing the Platform. Customer shall abide by, and Customer shall ensure that its Authorized Users abide by the TOU when using or accessing the Platform.
Billing Cooperation. If Customer selects Medical Billing Services on the applicable Order Form, Customer shall provide DayaMed and its designated billing services provider with all information, documentation, system access, payer enrollments, clearinghouse credentials, electronic health record access, practice management system access, and other assistance reasonably necessary to perform the Medical Billing Services. Customer shall promptly notify DayaMed of any changes that may affect billing or claims submission. The Parties shall coordinate billing attribution, eligible time records, coding support, correction of identified errors, and duplicate-billing prevention under the Medical Billing Services provisions of this Agreement and the applicable Order Form. Eligible time and activities shall satisfy the applicable code requirements; the same time shall not be counted toward multiple services where prohibited. No claim shall be submitted solely because a patient is enrolled or a PMPM fee is due.
Fees. Customer shall pay to DayaMed the fees set forth in the applicable Order Form ("Fees"). Schedule C does not impose separate fees; compensation and fee adjustments remain governed by the applicable Order Form and this Section 5.
Fee Structure and Adjustment. Customer shall pay the fixed Per Patient Per Month ("PMPM") Service Fees stated in the applicable Order Form for each Eligible Enrolled Patient receiving the applicable Services during a calendar month. An "Eligible Enrolled Patient" means a Participating Patient for whom required enrollment, eligibility, orders and consent have been established for the applicable Services and for whom DayaMed actually furnishes and documents Services during that month. Enrollment, inclusion on a roster, or unsuccessful outreach attempts alone do not establish that Services were furnished. Documented monitoring and care-management activities actually performed under the applicable order, care plan and approved protocols may constitute Services even if the patient does not complete every requested activity. No PMPM fee shall be charged for a patient who remains entirely inactive and receives no actual Services during the month. The fixed PMPM fee applies once for each applicable Service in a month in which actual Services are furnished, including a partial month, unless the Order Form expressly provides otherwise; a selected combined-service fee replaces the separate component fees as provided in Schedule A.
Monthly Reconciliation, Claims and Invoicing. Following the end of each calendar month, DayaMed shall reconcile documented Services and prepare the applicable CPT or HCPCS codes and supporting information for claims that satisfy applicable code and payer requirements. Where Medical Billing Services are selected, DayaMed or its designated billing provider shall submit those claims on Customer’s behalf; otherwise, Customer is responsible for submission. Claim preparation and submission shall proceed in parallel with monthly invoicing and shall not delay compliance with applicable filing deadlines. DayaMed shall issue the invoice in arrears at the beginning of the following month, identifying the applicable service month, charged patient count and PMPM rates, with supporting patient-level detail made available through a secure channel. Payment is due within thirty (30) days of the invoice date. These payment terms are intended to allow time for payer processing, but reimbursement timing and amounts are not guaranteed. Payment for actual Services furnished is not contingent upon claim submission, approval, collection, or the date Customer receives reimbursement. No claim may be submitted solely because a PMPM fee is due; fees and payer billing eligibility are determined separately.
The Parties acknowledge that reimbursement levels, payer mix, patient mix, regulatory requirements, program utilization, and operational costs may change over time. Accordingly, either Party may request a review of the Service Fees no more than once during any calendar quarter. Any requested adjustment shall be supported by reasonable justification and shall become effective only upon the Parties' mutual written agreement.
Unless otherwise agreed in writing, any approved adjustment to the Service Fees shall apply prospectively and become effective thirty (30) days following execution of the applicable written amendment.
Disputed Payments. If Customer wishes to dispute any invoiced Fees, Customer must do so via written statement to DayaMed no later than ten (10) days prior to the payment due date. Such notice must include a list of all disputed items and provide a reasonably detailed reason for dispute. Amounts not so disputed shall be deemed accepted and shall be paid when due. The parties shall seek to resolve all such disputes expeditiously and in good faith.
Interest. Any amounts payable by Customer that remain unpaid thirty (30) days after the invoice date shall be considered past due and will accrue interest at a rate of one and one-half percent (1.5%) per month or the maximum amount permitted by law, whichever is less.
Suspension. If any fees owed by Customer are more than thirty (30) days past due, DayaMed may, without limiting its other rights and remedies, suspend the Services until such amounts are paid in full, upon thirty (30) days’ written notice to Customer.
Taxes. All prices set forth in this Agreement are in U.S. Dollars and are exclusive of any applicable sales, use, value added, or other fees, governmental charges, or taxes of any nature (other than U.S. taxes on DayaMed’s net income), including penalties and interest, and all government permit or license fees assessed upon or with respect to any products sold, leased, or licensed to Customer and any services rendered to Customer. In the event that Customer is a tax-exempt organization under the Internal Revenue Code, Customer shall be exempt from certain taxes including, but not limited to, federal and state income taxes, state sales taxes, and federal excise taxes related to telecommunications services. Customer shall provide DayaMed with evidence of any such tax-exempt status.
DayaMed Intellectual Property. As between DayaMed and Customer, all right, title, and interest, including all Intellectual Property Rights, in the Platform, DayaMed Data, and any other DayaMed property or materials furnished or made available as part of the Services, and all modifications and enhancements of the same (“DayaMed Intellectual Property”), belong to and are retained solely by DayaMed or DayaMed’s licensors and providers, as applicable. Nothing in this Agreement is intended to or may be construed to transfer any such rights in any part of the Services to Customer other than as explicitly provided for in this Agreement. Customer shall not re-distribute the Platform other than as specifically provided for in this Agreement.
Developments. Except as otherwise explicitly set forth in this Agreement, all inventions, works of authorship, and developments conceived, created, written, or generated by or on behalf of DayaMed, whether solely or jointly, in connection with the Services (“DayaMed Developments”) and all Intellectual Property Rights in the same, shall be the sole and exclusive property of DayaMed. Customer agrees to execute any documents or take any actions as may reasonably be necessary, or as DayaMed may reasonably request, to perfect DayaMed’s ownership of the DayaMed Developments.
Trademarks. Nothing in this Agreement shall grant either Party ownership interest, license, or other rights to the other Party’s trade names, trademarks, or service marks, except as expressly provided in this Agreement.
Customer Data. As between DayaMed and Customer, all right, title and interest in the Customer Data belong to and are retained solely by Customer. Customer is solely responsible for the accuracy, quality, integrity, legality, reliability, and appropriateness of all Customer Data. Customer Data will be included in and treated as Customer’s Confidential Information under this Agreement.
DayaMed License. Customer grants to DayaMed a limited, non-exclusive, royalty-free, worldwide license to (i) Use, reproduce, aggregate and modify the Customer Data and to perform all acts with respect to the Customer Data as may be necessary for DayaMed to provide the Services to Customer; (ii) Use or modify the Customer Data to create De-identified Data; and (iii) Use Customer’s name, logo, and trademark for marketing purposes upon written consent of Customer. DayaMed intends to use De-identified Data, aggregated with the de-identified data of other DayaMed customers, to enable DayaMed to provide more targeted, accurate, and useful insights to its customers.
Accuracy of Customer Data. As between DayaMed and Customer, Customer is solely responsible for the accuracy, quality, integrity, legality, reliability, and appropriateness of all Customer Data. Customer Data will be included in and treated as Customer’s Confidential Information under this Agreement.
Third-Party Data. The Services and Documentation may contain material, data, or information provided by third parties (“Third-Party Data”). DayaMed does not control Third-Party Data and is not responsible for its content. DayaMed’s inclusion of Third-Party Data in the Services does not imply any endorsement of the information and DayaMed makes no representations or warranties with respect to any Third-Party Data.
Feedback. DayaMed owns all right, title, and interest in and to any suggestion, enhancement, request, recommendation, or other feedback related to the Platform or the Services provided by Customer (any “Feedback”). Feedback is not Customer’s Confidential Information.
Confidential Information Defined. “Confidential Information” means all non-public technical and non-technical information disclosed by one Party (the “Disclosing Party”) to the other Party (the “Receiving Party”) in any form or medium, that the Disclosing Party identifies as confidential or that by the nature of the circumstances surrounding the disclosure and/or receipt ought to be treated as confidential and proprietary information. Confidential Information includes, without limitation, (a) techniques, inventions (whether or not patented or patentable), know-how, processes, algorithms, software programs, software source and object codes and documents, APIs, and other creative works (whether or not copyrighted or copyrightable); (b) financial information, customer lists, business forecasts, and marketing plans and information; (c) the business relationships and affairs of either party and its clients, patients, and referral sources; (d) the internal policies and procedures of either Party; (e) proprietary or confidential information of any third party who may disclose such information to Disclosing Party or Receiving Party in the course of Disclosing Party’s business; and (f) the terms of this Agreement. DayaMed’s Confidential Information includes the Platform and DayaMed Data. Confidential Information of Customer includes Customer Data. Confidential Information also includes all summaries and abstracts of Confidential Information. Confidential Information excludes PHI, which must be protected according to the BAA.
Exceptions. The term “Confidential Information” shall not include any information which, as evidenced by Receiving Party’s records: (a) was known by the Receiving Party prior to receipt from the Disclosing Party either itself or through receipt directly or indirectly from a source with no obligation of confidentiality to the Disclosing Party; (b) was developed by the Receiving Party without direct or indirect use of, reference to, or reliance on the Disclosing Party’s Confidential Information; or (c) becomes publicly known or otherwise ceases to be secret or confidential, except as a result of a breach of this Agreement or any obligation of confidentiality by the Receiving Party.
Confidential Information Terms. The Receiving Party will keep in confidence and trust all of the Disclosing Party’s Confidential Information. The Receiving Party will not use the Disclosing Party’s Confidential Information other than as necessary to fulfill the Receiving Party’s obligations or to exercise the Receiving Party’s rights under this Agreement. Either Party may disclose the other Party’s Confidential Information upon the order of any competent court or government agency; provided that, prior to disclosure and to the extent possible, the receiving Party must (a) assert the confidential nature of the Confidential Information to the agency; (b) immediately notify the Disclosing Party in writing of the order or request; and (c) cooperate fully with the Disclosing Party in protecting against, at Disclosing Party’s sole expense, any such disclosure and/or narrowing the scope of the compelled disclosure. Each Party agrees to secure and protect the other Party’s Confidential Information with the same degree of care and in a manner consistent with the maintenance of such Party’s own Confidential Information (but in no event less than reasonable care). The Receiving Party will not disclose Confidential Information of the Disclosing Party to any person or entity other than its officers, employees, affiliates, and agents who need access to such Confidential Information to affect the intent of this Agreement and who are subject to confidentiality obligations at least as stringent as the obligations set forth in this Agreement.
Injunctive Relief. The Parties agree that any unauthorized disclosure of Confidential Information may cause immediate and irreparable injury to the Disclosing Party and that, in the event of such breach, the Disclosing Party will be entitled, in addition to any other available remedies, to seek immediate injunctive and other equitable relief, without bond and without the necessity of showing actual monetary damage.
HIPAA Compliance. Each Party, to the extent applicable, will comply with laws and regulations applicable to the privacy and security of individually identifiable health information, including but not limited to state laws and regulations and the Health Insurance Portability and Accountability Act (“HIPAA”), the Health Information Technology for Economic and Clinical Health Act (“HITECH”), and/or regulations promulgated thereunder (“HIPAA Regulations”). The BAA further describes the parties’ obligations with respect to compliance with HIPAA, HITECH, and HIPAA Regulations. Schedule B governs PHI matters, including those arising from Clinical Services under Schedule C.
Security. Customer is responsible implementing and complying with protocol to ensure any Authorized User’s access and use of the Platform complies with any and all applicable state and federal laws and regulations. Customer agrees to immediately notify DayaMed of any unauthorized use of any account or login and password issued to an Authorized User, or any other breach of security known to Customer. DayaMed will have no liability for any loss or damage arising from Customer’s failure to comply with the terms set forth in this Section. Customer will ensure its Authorized Users do not circumvent or otherwise interfere with any user authentication or security of the Platform.
Without Cause. Either Party may terminate this Agreement without cause upon ninety (90) days’ written notice to the other Party.
Mutual Agreement. This Agreement shall terminate upon the mutual written agreement of Customer and DayaMed as of the date of signature or other effective date set forth on the written instrument.
For Cause.
Material Breach. Either Party may terminate this Agreement following a material breach of this Agreement by the other Party which is not cured during the Cure Period. The non-breaching Party shall notify the breaching Party of the breach in writing and the breaching party shall have thirty (30) days (the “Cure Period”) to cure the breach following receipt of the notification. If the breaching Party fails to cure the breach within the Cure Period, then the non-breaching Party may terminate this Agreement upon written notice to the breaching Party.
Other Cause. DayaMed may terminate this Agreement immediately by providing written notice to Customer upon the occurrence of any of the following events:
DayaMed reasonably determines that Customer and/or its Authorized User(s) have been or are engaged in unlawful activity associated with the use of the Platform and/or the Services;
The indictment or conviction of Customer or its principals, employees, or agents for any felony or misdemeanor involving moral turpitude;
The filing, with respect to Customer, of a voluntary or involuntary petition in bankruptcy if such petition is not dismissed within thirty (30) days of such filing;
Customer comes under investigation and/or excluded from participation in a state or federal healthcare program; and/or
Upon the appointment of a receiver or trustee to take possession of all, or substantially all, of Customer’s assets, if such appointment is not terminated within thirty (30) days.
Effect of Termination. Unless otherwise stated below, upon expiration or termination of this Agreement for any reason, (a) neither Customer nor Authorized Users shall use or access, directly or indirectly, the Platform; (b) DayaMed’s obligation to perform Services shall cease; and (c) all fees and other amounts owed to DayaMed accrued prior to expiration or termination will be immediately due and payable. Further, if Customer has made any copies of any DayaMed property or materials furnished or made available under this Agreement, Customer shall, within thirty (30) days of the effective date of the expiration or termination, either destroy or return to DayaMed all such copies along with a certificate signed by Customer that all such copies have been either destroyed or returned, respectively, and that no copy or any part of the Platform, data, or other materials has been retained by Customer in any form. Discontinuation of Clinical Services shall include an orderly patient and record transition under Schedule C, Section 11, without extending services beyond termination unless separately agreed in writing or required by applicable law. Access reasonably necessary for an agreed transition shall be arranged by the Parties subject to Schedule B.
Return of Customer Data. Within thirty (30) days following the effective date of termination or expiration and upon Customer’s written request, DayaMed will make Customer Data in its possession available to Customer. Clinical record transition shall also be coordinated under Schedule C, Section 11, and PHI return or destruction remains governed by Schedule B.
Return of DayaMed Data. If Customer has made any copies of any DayaMed property, data, or materials furnished or made available under this Agreement, Customer shall, within thirty (30) days of the effective date of the expiration or termination, either destroy or return to DayaMed all such copies along with a certificate signed by Customer that all such copies have been either destroyed or returned, respectively, and that no copy or any part of the Platform, data, or other materials has been retained by Customer in any form.
Mutual Representations and Warranties. Each Party represents, warrants and covenants that: (a) to its knowledge, it has the full power and authority to enter into this Agreement and to perform its obligations hereunder, without the need for any consents, approvals, or immunities not yet obtained; (b) its acceptance of and performance under this Agreement will not breach any oral or written agreement with any third party or any obligation it owes to any third party; and (c) it will comply with any and all applicable local, state, and/or national laws or regulations applicable to such party, including, without limitation, those related to PHI, Covered Entities, and Business Associates as each term is defined under HIPAA, and to any other laws or regulations regarding data privacy and transmission of personal data.
Practice of Medicine. DayaMed provides the selected clinical support Services through appropriately qualified personnel under Schedule C and does not independently exercise authority reserved by law to a physician or other qualified practitioner. Customer and its qualified practitioners retain authority over diagnosis, prescribing, treatment decisions, and required personal service components. DayaMed remains responsible for its own Services and personnel under this Agreement. DayaMed does not provide 24/7 continuous, synchronous, or emergency monitoring or alerting. Platform information does not replace practitioner judgment.
Third-Party Materials. Customer understands and agrees that using, accessing, downloading, or otherwise obtaining information, materials, or data through the platform from a source other than DayaMed (“Third-Party Materials”) is at its own discretion and risk and that customer will be solely responsible for any damage to its or its authorized users’ property or loss of data that results from the download or use of such material or data.
Disclaimer. Except for the express warranties set forth in this Agreement, the Services are provided on an as-is basis. Customer’s use of the Platform and purchase of the Services are at its own risk. DayaMed does not make, and hereby disclaims, any and all other express, statutory, and implied warranties, including without limitation, warranties of merchantability, fitness for a particular purpose, noninfringement and accuracy (of data or any other information or content), and any warranties arising from a course of dealing, usage, or trade practice. Any warranties made by DayaMed are for the benefit of customer only and not for the benefit of any third-party. The Platform may be subject to limitations, delays, and other problems inherent in the use of the internet and electronic communications, such as delays caused by third-party network providers, that are outside DayaMed’s control. DayaMed is not responsible for any delays, delivery failures, or other damages resulting from such problems. The entire risk arising out of use or performance of the Platform, including without limitation any information, data, products, processes, and other matters referenced by the services remains with the Customer. Except as expressly provided herein, DayaMed does not guarantee continuous, error-free, virus-free, or secure operation and access to the Platform.
Medical Billing Disclaimer. If Customer selects Medical Billing Services, DayaMed and its designated billing services provider shall use commercially reasonable efforts to prepare and submit accurate and timely claims based on information provided by Customer and documentation of services performed by DayaMed. Customer acknowledges that reimbursement is determined by applicable payer policies, patient eligibility, medical necessity, documentation, and other factors beyond DayaMed's control. Accordingly, DayaMed does not guarantee claim approval, reimbursement, payment amounts, or collection of any receivable. Billing responsibilities and supporting documentation shall be coordinated under the Medical Billing Services provisions of this Agreement and the applicable Order Form.
Basis of the Bargain. Customer acknowledges and agrees that DayaMed has offered its services and entered into this Agreement to which it is a party in reliance upon the warranty disclaimers and the limitations of liability set forth herein, that the warranty disclaimers and the limitations of liability set forth herein reflect a reasonable and fair allocation of risk between Customer and DayaMed, and that the warranty disclaimers and the limitations of liability set forth herein form an essential basis of the bargain between Customer and DayaMed. Customer acknowledges and agrees that DayaMed would not be able to provide the services to Customer on an economically reasonable basis without these limitations.
Insurance. During the Term, DayaMed and Customer shall maintain general and professional liability insurance in amounts of not less than One Million Dollars ($1,000,000.00) per occurrence and Three Million Dollars ($3,000,000.00) in the aggregate, or in any greater minimum amount if required by State law. Such insurance shall be maintained via national carriers with ratings customary for customers in the industries in which the parties operate. Clinical personnel qualifications and credentialing shall be maintained as provided in Schedule C; this Schedule does not establish separate insurance limits or indemnification obligations.
Indemnification by Customer. Customer shall indemnify and hold harmless DayaMed and its officers, directors, employees, and agents (“DayaMed Indemnified Parties”), from and against any and all damages, liabilities, penalties, interest, fines, losses, costs, and expenses (including reasonable attorneys’ fees and expenses) (“Losses”), arising, directly or indirectly, out of or relating to any claim, action, or proceeding (a “Claim”) brought by a third party based on (a) the improper use or operation of the Services (and any third party software provided to Customer pursuant to this Agreement) by Participating Patients, Customer and/or Authorized Users, including, without limitation, any non-authorized use of Customer’s user logins, except to the extent that any such Loss was due to the gross negligence or willful misconduct of DayaMed; (b) a breach of the Agreement and/or the TOU by Customer or any of its Authorized Users; (c) the accuracy, quality, integrity, legality, reliability, or appropriateness of Customer Data or any other content or data introduced to any part of the Services by any Authorized User; (iv) violation of any applicable law, rule, or regulation by Customer or any of the Authorized Users; (v) the diagnosis and/or treatment of any of Customer’s patients; and/or (vi) the negligent acts or willful misconduct of Customer or its personnel. Customer will pay all Losses (whether by settlement or award of final judicial judgment) incurred by the DayaMed Indemnified Parties from any such Claim.
Mutual Indemnification. Each Party (the “Indemnifying Party”) agrees to defend the other Party, its affiliates and each of their respective officers, directors, employees, contractors and agents (each an “Indemnified Party”) from and against any Claim brought by a third party (“Third Party Claim”) to the extent such Third Party Claim results from the Indemnifying Party’s breach of this Agreement or the negligence, willful misconduct or fraud or violation of law on the part of the Indemnifying Party, its officers, directors, employees, agents or other representatives in connection with this Agreement. The Indemnifying Party will indemnify and hold harmless the Indemnified Party from any Losses incurred by or levied against such Indemnified Party as a result of such Third-Party Claim.
Indemnification Procedure. If an Indemnified Party (such term including, for purposes of this Section 10.d, a DayaMed Indemnified Party), as applicable under the provisions of 10.b and/or 10.c, such party shall: (a) provide written notice to the Indemnifying Party of any Claim within thirty (30) days after the Indemnified Party has knowledge of such Claim (except that failure to timely provide such notice will relieve the Indemnifying Party of its obligations only to the extent the Indemnifying Party is materially prejudiced as a direct result of such delay); (b) give the Indemnifying Party sole control over the defense of the Claim(s) and any related settlement negotiations, subject to the Indemnified Party’s participation and settlement approval rights below; and (c) cooperate and, at the Indemnifying Party’s request and expense, assisting in such defense. Notwithstanding the foregoing, the Indemnified Party may participate at its own expense in the defense and any settlement discussions and will have approval rights over any settlement agreement that involves an admission of fault by the Indemnified Party or imposes non-monetary obligations on the Indemnified Party; provided, however, that such approval will not be unreasonably withheld.
IP Infringement Claims. In the event of a claim that the Platform infringes or misappropriates the patent, trade secret, trademark, copyright, or other Intellectual Property Rights of any third party, DayaMed may, at its election, and sole expense, (a) modify the Platform so that such Platform is non-infringing and functionally equivalent; or (b) obtain the right for Customer and Customer’s patients to continue using the Platform at no additional cost to Customer. If none of the foregoing is commercially practicable, either Party may immediately terminate this Agreement upon reasonable notice to the other Party. Both Parties acknowledge and agree that the remedies set forth in this paragraph constitute the Parties’ only available remedies and DayaMed’s only obligation with respect to an Infringement Claim.
No Consequential Damages. Neither party will be liable for any indirect, incidental, special, consequential or punitive damages, or any damages for lost data, business interruption, lost profits, lost revenue, or lost business arising out of or in connection with this agreement, including without limitation any such damages arising out of DayaMed’s provision or Customer’s use of the Platform or the results thereof, even if a party has been advised of the possibility of such damages. In no event will DayaMed be liable for the cost of procurement of substitute goods or services.
Limits on Liability. In no case will either party be liable for any aggregate amount greater than the amounts paid and payable by Customer to DayaMed under this agreement during the twelve (12) month period preceding the date on which the claim first accrued, without regard to whether such claim is based in contract, tort (including negligence), product liability or otherwise.
Essential Purpose. CUSTOMER ACKNOWLEDGES THAT THE TERMS IN THIS SECTION (LIMITATION OF LIABILITY) ARE A BARGAINED FOR REASONABLE ALLOCATION OF THE RISK BETWEEN THE PARTIES AND WILL APPLY (A) TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, AND (B) EVEN IF AN EXCLUSIVE OR LIMITED REMEDY STATED HEREIN FAILS OF ITS ESSENTIAL PURPOSE.
Exceptions. The limitations and exclusions of certain damages set forth in subsections 11.a and 11.b will not apply to Losses caused by a Party’s gross negligence or willful misconduct.
Limitation of Action. No action (regardless of form) arising out of this Agreement may be commenced by Customer against DayaMed more than two (2) years after the cause of action arose. Actions arising out of Schedule B are subject to the limitation period expressly stated in Schedule B, Section 6.3.
Affiliates, Subcontractors and Vendors. Some or all of the Services, including support, may be provided by DayaMed’s affiliates, agents, subcontractors, and information system vendors. The rights and obligations of DayaMed may be, in whole or in part, exercised or fulfilled by the foregoing entities. Personnel performing Clinical Services remain subject to Schedule C’s qualifications, scope-of-practice, credentialing, and supervision requirements, and any subcontractor with access to PHI remains subject to Schedule B.
Notices. Any notice pursuant to this Agreement must be in writing and must be sent by email to such Party at the email address or address set forth in the applicable services order form accompanying this Agreement, or at such other address as such Party specifies in writing. Notices are effective when sent by email on the date sent (if within receiving party’s normal business hours) or the following business day (if sent after such normal business hours).
Amendment. Except as may otherwise be specified in this Agreement, this Agreement may be modified, changed, or amended only by a written amendment mutually agreed to and signed by both Parties. Routine updates to personnel or practitioner rosters, patient assignments, approved protocols, thresholds, and operational workflows permitted by Schedule C do not require a signed amendment unless required by law or payer rules. Changes to selected Services, pricing, or contractual risk allocation remain subject to this amendment requirement.
Waiver; Severability. No waiver of any term or right in this Agreement shall be effective unless in writing, signed by an authorized representative of the waiving Party. The failure of either Party to enforce any provision of this Agreement shall not be construed as a waiver or modification of such provision, or impairment of its right to enforce such provision or any other provision of this Agreement. If any provision or portion of this Agreement shall be rendered by applicable law or held by a court of competent jurisdiction to be illegal, invalid, or unenforceable, the remaining provisions or portions shall remain in full force and effect.
Governing Law & Venue. This Agreement will be construed according to, and the rights of the Parties will be governed by, the laws of the State of Nevada, without reference to its conflict of laws rules. Exclusive forum and venue to enforce final Dispute Resolution judgment, as set forth under Section 12.l shall be in state or federal courts in Nevada. The Parties waive any objections or defenses it may have based upon an inconvenient forum.
Assignment. Neither Party may assign or transfer this Agreement or any additional applicable Terms & Conditions without the prior written consent of the other Party; provided, however, that DayaMed may assign or transfer this Agreement without Customer’s consent to any of DayaMed’s affiliates, subsidiaries, or entities controlled by or under common control with DayaMed, or in the event of a merger, change of control, or sale of substantially all of its assets. This Agreement will bind the Parties and their respective successors and permitted assigns and will inure to the benefit of the Parties and their respective permitted successors and assigns.
Force Majeure. If any Party is unable to perform any of its obligations under this Agreement (with the exception of payment obligations) because of any cause beyond the reasonable control of and not the fault of the Party invoking this section, including any act of God, fire, casualty, flood, earthquake, war, strike, lockout, epidemic or pandemic, destruction of production facilities, riot, insurrection, or material unavailability, and if the non-performing Party has been unable to avoid or overcome its effects through the exercise of commercially reasonable efforts, such non-performing Party will give prompt notice to the other Party, its performance will be excused, and the time for its performance will be extended for the period of delay or inability to perform due to such occurrences. If performance is extended under this section for more than sixty (60) days, then at any time before reinstatement of the performance, the other Party may terminate this Agreement upon notice to the non-performing Party.
Relationship of the Parties. The sole relationship between the Parties is solely that of independent contractors. This Agreement will not create a joint venture, partnership, agency, employment, or other relationship between the Parties. DayaMed’s personnel independence and staffing responsibilities are further described in Schedule C, Section 4. Practitioner supervision does not, by itself, create an employment relationship between Customer and DayaMed personnel.
Internal Allocation of Fees. Customer acknowledges that DayaMed may provide the Services, including access to and use of DayaMed’s software, through one or more affiliated entities, including management services organizations (“MSOs”), professional corporations (“PCs”), or other affiliated entities. Customer's sole obligation under this Agreement is to pay the Service Fees set forth in the applicable Order Form. DayaMed may internally allocate, apportion, invoice, receive, and distribute Service Fees among its affiliated entities in accordance with its corporate structure, applicable law, and the operational responsibilities of such entities. Such internal allocation shall not increase Customer's financial obligations, alter the scope of the Services, or require Customer to make separate payments to multiple entities unless otherwise agreed in writing.
Customer acknowledges that certain Services, including medical billing and revenue cycle management, may be performed by GAPP Healthcare Solutions, LLC or another designated billing services provider acting on DayaMed's behalf.
Publicity. DayaMed may not use the names or trademarks of Customer in any advertising, publicity, endorsement, or promotion , other than for internal company communications, unless Customer has provided prior written consent for the particular use contemplated, which shall not be unreasonably withheld.
Survival. Any term of this Agreement that contemplates performance after termination of this Agreement, or that would be reasonably interpreted to survive termination, will survive expiration or termination, and continue until fully satisfied or until the termination of any applicable statute of limitations.
Dispute Resolution. In case of disputes in connection with the negotiation, execution, interpretation, performance, or non-performance of this Agreement, the Parties agree a three-stage dispute resolution process (collaboration, mediation, arbitration). First, a party alleging a dispute shall provide notice of such dispute and promptly to assign an executive point of contact with knowledge of the Agreement to engage in good faith collaborative discussions to resolve the dispute in an efficient and timely manner. Second, if the parties are unable to resolve the dispute through collaboration within 15 days of notice of the dispute, either party may seek non-binding mediation, which shall be conducted remotely by a single mediator selected by the Parties. If the Parties fail to agree on the mediator within thirty (30) days of the date one of them invokes this provision, either Party may apply to the American Arbitration Association to make the appointment. The mediator shall conduct the proceedings pursuant to the rules of the American Arbitration Association, as they exist at the time of the dispute. Third, in the event that any such mediation does not resolve the dispute, unless the dispute is otherwise settled, the parties agree to the dispute shall be determined by binding and final arbitration in Nevada by a single arbitrator selected by the Parties (or by the American Arbitration Association if the Parties cannot agree) in accordance with the law of the State of Nevada and the rules of the American Arbitration Association then in effect. The costs of arbitration, including the arbitrator’s fees, shall be shared equally between the Parties. The arbitrator shall have the right to award costs and fees to the prevailing party in the dispute. Notwithstanding the above, either Party may seek equitable relief, including injunctive relief, to enforce the terms of this Agreement without first resorting to mediation or arbitration. This provision shall survive termination or expiration of the Agreement.
Entire Agreement; Order of Precedence. This Agreement, including the applicable Order Form, Schedule A—Services List & Additional Terms, Schedule B—Business Associate Agreement, and Schedule C—Clinical Services and Supervision, constitutes the entire agreement between the Parties relating to this subject matter and supersedes prior or simultaneous understandings, representations, discussions, negotiations, and agreements, whether written or oral. Schedule B controls privacy, security, and PHI matters. Schedule C controls clinical supervision, personnel qualifications, practitioner attribution, clinical documentation, and escalation matters. The Order Form controls selected Services, pricing, expressly stated service-term and non-renewal provisions, and expressly agreed service-specific billing arrangements, subject to applicable law and payer requirements. The main Services Agreement controls all other general commercial terms, including insurance, indemnification, limitations of liability, governing law, and general termination rights. No schedule creates separate fees or a separate term unless expressly agreed in the Order Form.
Counterparts. This Agreement may be executed electronically or by signature in one or more counterparts. Each counterpart will be an original, but all such counterparts will constitute a single instrument. Execution of the Agreement or Order Form expressly incorporating Schedules A, B, and C accepts those schedules without separate signatures.
[End of Services Agreement – Schedules Attached]
This Schedule A is part of the DayaMed Services Agreement. It applies to the Services selected on the Order Form. Clinical Services are also subject to Schedule C, and all PHI is subject to Schedule B. Bracketed text marks open business points to be completed or deleted before signing.
1. Administrative Access (All Services)
Platform Access. DayaMed grants Customer and its Authorized Users access to the Platform to review, analyze and record patient information, subject to the Terms of Use. If the Terms of Use conflict with the Agreement, the Agreement controls. Customer may not extend access to affiliates without DayaMed’s written consent.
Implementation and Training. DayaMed will configure the Platform for Customer, train Authorized Users, and, where Customer’s EHR supports it, implement a bidirectional FHIR interface to exchange (a) patient history needed to apply Customer’s protocols, (b) encounter, service, monitoring and adherence records, and (c) billing data. The system of record will be designated under Schedule C, Section 8.
Support. DayaMed provides technical support by telephone and email on weekdays, 9:00 a.m.–6:00 p.m. Central Time, excluding U.S. federal holidays (“Support Hours”). DayaMed will acknowledge helpdesk tickets within [one (1)] business day and use commercially reasonable efforts to resolve them promptly, prioritizing Platform outages.
Clinical Hours. DayaMed Clinical Personnel (as defined in Schedule C) are available on the same weekday schedule (“Clinical Hours”). Services are not available outside Clinical Hours unless the Parties agree in writing.
2. Terms Common to All Clinical Services
Customer Responsibilities. Customer will (a) determine patient eligibility and medical necessity and provide required orders; (b) approve each care plan and protocol; (c) designate Supervising Practitioners, a Clinical Contact and backup coverage; (d) respond timely to escalations; and (e) provide 24/7 access to the patient’s care team where the selected program requires it.
DayaMed Responsibilities. DayaMed will provide qualified Clinical Personnel who conduct patient outreach, perform the activities described below within Customer-approved protocols, document time and activities as required by Schedule C, Section 8, and escalate findings as required by Schedule C, Section 7.
Consent and Cost-Sharing. Required patient consent will be obtained and documented before services begin, as provided in Schedule C, Section 9. Consent must include notice of the patient’s right to stop services and of any applicable patient cost-sharing. Neither Party will waive or routinely forgive patient cost-sharing except as permitted by law.
No Emergency Services. The Services are not an emergency-response or continuous-surveillance system. DayaMed will direct patients to call 911 in an apparent emergency.
Time Tracking and Billing Integrity. DayaMed will record the time and activity for each service. The same time will not be counted toward more than one service where prohibited. Customer will confirm that no other practitioner is billing a conflicting service for the same patient and period. Enrollment or payment of a PMPM fee does not by itself make a service billable; a claim may be submitted only when the applicable code and payer requirements are met.
3. Remote Physiologic Monitoring (RPM)
Scope. DayaMed supports monitoring of physiologic parameters (such as blood pressure, glucose, weight and oxygen saturation) that Customer orders for a Participating Patient, using devices that meet the definition of a medical device under applicable FDA rules and that transmit data automatically to the Platform.
Devices. DayaMed will supply, ship and, where needed, replace the devices listed in the Order Form; device costs are included in the PMPM fee; and DayaMed will request return of devices upon unenrollment.
Patient Setup. DayaMed will provide patient onboarding, device-setup education and troubleshooting during Support Hours.
Customer Prerequisites. Customer is responsible for confirming an established patient relationship, a valid order, medical necessity, and the monitoring parameters and escalation thresholds for each patient.
Monitoring and Management. During Clinical Hours, DayaMed Clinical Personnel will review transmitted data, contact patients by live, interactive communication where the care plan requires, document time spent, and escalate findings per protocol. DayaMed is not responsible for data that devices or patients fail to transmit.
4. Remote Therapeutic Monitoring (RTM)
Scope. DayaMed supports monitoring of therapeutic data, including medication adherence collected through the Patient Mobile App, as ordered by Customer. Sections 3.3 through 3.5 apply to RTM with the necessary changes.
Billing Eligibility. Customer determines whether data collected qualifies for any billing code. [DayaMed will identify in writing which Platform data elements it represents are designed to meet current RTM requirements.]
5. Chronic Care Management (CCM)
Eligibility. Customer will confirm that each CCM patient has two or more chronic conditions expected to last at least twelve months or until death, and that place the patient at significant risk, consistent with applicable Medicare or payer criteria.
Services. DayaMed Clinical Personnel will, under Customer’s supervision and care plan: (a) help develop and maintain a comprehensive care plan; (b) contact patients regularly to assess medical, psychosocial and functional needs; (c) provide care coordination and transition support; (d) oversee medication self-management and reconcile reported medications against Customer’s EHR quarterly; (e) maintain a structured record; and (f) keep a phone line open during Clinical Hours.
Continuity and Access. Customer remains responsible for 24/7 access to the care team and for continuity with a designated team member. DayaMed will tell patients how to reach Customer outside Clinical Hours.
Higher-Level Services. Complex CCM and any service requiring a practitioner’s personal time are included only if stated in the Order Form.
6. Principal Care Management (PCM)
PCM is available for patients with a single serious, high-risk condition. Section 5 applies with the necessary changes, using a condition-specific care plan. Customer will not enroll a patient in PCM and CCM for the same period where payer rules prohibit it.
7. Advanced Primary Care Management (APCM)
APCM is a Customer-led primary care model. Customer is responsible for meeting APCM requirements and for patient-level eligibility and risk-tier determination. DayaMed will provide only the supporting activities listed in the Order Form [such as patient outreach, care coordination, care-plan documentation and population tracking]. Customer will not enroll a patient in APCM together with services that payer rules prohibit billing in the same period.
8. Behavioral Health Integration (BHI)
DayaMed Clinical Personnel will help develop a behavioral health care plan, conduct regular outreach, facilitate access to psychotherapy, pharmacotherapy, counseling or psychiatric consultation, track patient progress using Customer-approved tools, and coordinate with Customer’s team. Customer will designate the billing practitioner and, where required by the service model, a psychiatric consultant and behavioral health care manager.
9. Transitional Care Management (TCM)
Following a qualifying discharge identified by Customer, DayaMed will make outreach contact within the timeframe required by applicable TCM rules, support medication reconciliation, provide patient education and follow-up scheduling support, and coordinate with community providers. Customer’s billing practitioner personally furnishes the required face-to-face visit and medical decision-making, and Customer is responsible for TCM eligibility and timing.
10. RPM + CCM Combined Services
When selected, Sections 2, 3 and 5 apply together. DayaMed will track RPM and CCM time separately, will not count the same time toward both, and will invoice the single combined PMPM fee stated in the Order Form.
11. Medical Billing Services (If Selected)
Scope. DayaMed or its designated billing provider (currently GAPP Healthcare Solutions, LLC) will perform registration support, eligibility verification, charge capture, claim preparation and submission, payment posting, denial follow-up, and reporting for the selected Services, based on Customer’s clinical decisions and DayaMed’s documentation.
Billing Entity. Customer is the billing entity unless the Order Form states another lawful arrangement. Claims will use the identifiers required by the payer.
Payments. All payer payments will be deposited directly into an account in Customer’s name. DayaMed and its billing provider will not receive or hold payer funds, and Customer retains control of all payer enrollments and credentials.
Accuracy and Review. Customer will review and approve claims or code selections where its compliance policies or payer rules require. [DayaMed will correct claim errors caused by its documentation at no additional charge and will cooperate in payer audits and appeals.]
No Guarantee. Reimbursement depends on payer policy, eligibility and documentation. DayaMed does not guarantee claim approval or payment.
Billing Provider. DayaMed will require its billing provider to protect PHI under Schedule B and remains responsible for its performance.
[End of Schedule A]
Pursuant to the Health Insurance Portability and Accountability Act of 1996, as amended (“HIPAA”), Customer (“Covered Entity”) and DayaMed and any of its corporate affiliates (“Business Associate”), enter into this Business Associate Agreement (“BAA”) as of the Effective Date identified on the Order Form. Covered Entity and Business Associate may be referred to collectively as the “Parties” and individually as a “Party.”
This BAA addresses the HIPAA requirements with respect to “business associates,” as defined under the privacy, security, breach notification, and enforcement rules at 45 C.F.R. Part 160 and Part 164 (“HIPAA Rules”). A reference in this BAA to a section in the HIPAA Rules means the section as in effect or as amended.
1. Preamble and Definitions
Purpose of BAA. This BAA is intended to ensure that Business Associate will establish and implement appropriate safeguards for the Protected Health Information (“PHI”) (as defined under the HIPAA Rules) that Business Associate may receive, create, maintain, use, or disclose in connection with the functions, activities, and services that Business Associate performs for Covered Entity. The functions, activities, and services that Business Associate performs for Covered Entity are defined in the DayaMed Services Agreement (the “Underlying Agreement”). The Underlying Agreement includes Schedule C—Clinical Services and Supervision; PHI used in performing those Services remains subject to this BAA.
Pursuant to changes required under the Health Information Technology for Economic and Clinical Health Act of 2009 (the “HITECH Act”) and under the American Recovery and Reinvestment Act of 2009 (“ARRA”), this BAA also reflects federal breach notification requirements imposed on Business Associate when “Unsecured PHI” (as defined under the HIPAA Rules) is acquired by an unauthorized party and the expanded privacy and security provisions imposed on business associates.
Definitions. Defined terms used in this Agreement are denoted with initial capital letters. Unless the context clearly indicates otherwise, the following terms in this BAA shall have the same meaning as those terms in the HIPAA Rules: Administrative Safeguards, Availability, Breach, Confidentiality, Data Aggregation, Designated Record Set, Disclosure, Electronic Media, Electronic Protected Health Information (“ePHI”), Healthcare Operations, Individual, Individually Identifiable Health Information, Integrity, Minimum Necessary, Notice of Privacy Practices, Physical Safeguards, Protected Health Information, Required By Law, Secretary, Security Incident, Subcontractor, Technical Safeguards, Unsecured PHI, Uses and Disclosures, and Workforce. A change to the HIPAA Rules which modifies any defined term, or which alters the regulatory citation for a definition will be deemed incorporated into this BAA.
Breach Notification Rule. A reference in this BAA to the Breach Notification Rule means Part 2, Subtitle D of the HITECH Act and Notification in the Case of Breach of Unsecured Protected Health Information at 45 C.F.R. Part 164 Subpart D.
Privacy Rule. A reference in this BAA to the Privacy Rule means the standards for Privacy of Individually Identifiable Health Information at 45 C.F.R. Part 160 and Subparts A and E of Part 164.
Security Rule. A reference in this BAA to the Security Rule means the Security Standards for the Protection of Electronic Protected Health Information at 45 C.F.R. Part 160 and Subparts A and C of Part 164.
2. Uses and Disclosures of PHI by Business Associate
General Uses and Disclosures of PHI Pursuant to the Underlying Agreement. Except as otherwise limited in this BAA, Business Associate may use or disclose PHI to perform functions, activities, or services for, or on behalf of, Covered Entity, as specified in the Underlying Agreement, provided that such use or disclosure would not violate the Privacy Rule if done by Covered Entity.
Permitted Uses of PHI by Business Associate. Except as otherwise limited in this BAA, Business Associate may use PHI for the following purposes: (i) the proper management and administration of Business Associate or to carry out the legal responsibilities of Business Associate; (ii) as Required by Law; (iii) to de-identify PHI in accordance with 45 C.F.R. § 164.514(b) and use such de-identified data for any reason not prohibited by applicable law; and (iv) provide Data Aggregation services relating to the Healthcare Operations of the Covered Entity.
Permitted Disclosures of PHI by Business Associate. Except as otherwise limited in this BAA, Business Associate may disclose PHI for the following purposes: (i) the proper management and administration of Business Associate, provided that the disclosures are Required by Law or Business Associate obtains reasonable assurances from the person to whom the information is disclosed that it will remain confidential and will be used or further disclosed only as Required by Law or for the purpose for which it was disclosed to such person, and that person agrees to notify Business Associate of any instances of which it is aware in which the confidentiality of the information has been breached; and (ii) to report violations of law to appropriate federal and state authorities, consistent with 45 C.F.R. § 164.502(j)(l).
Prohibited Uses and Disclosures of PHI by Business Associate. Business Associate may not use or disclose PHI in a manner that would violate Subpart E of 45 C.F.R. Part 164 if done by the Covered Entity; provided, further, that Business Associate may not use or disclose PHI for the purpose of marketing, as such term is defined at 45 C.F.R. § 164.501, unless Business Associate has obtained an authorization from the Individual in accordance with 45 C.F.R. § 164.508(a)(3).
3. Obligations of Business Associate
Appropriate Safeguards. Business Associate agrees to use appropriate safeguards and comply with Subpart C of 45 C.F.R. Part 164 with respect to ePHI to prevent use or disclosure of PHI other than as provided for by the Underlying Agreement and this BAA. To the extent applicable, Business Associate will implement the Administrative Safeguards (45 C.F.R. § 164.308), Physical Safeguards (45 C.F.R. § 164.310), and Technical Safeguards (45 C.F.R. § 164.312) to reasonably and appropriately protect the confidentiality, integrity, and availability of ePHI that it creates, receives, maintains, or transmits on behalf of Covered Entity as required by the Security Rule.
Privacy Rule Requirements. Except as expressly provided in the Underlying Agreement or this BAA, Business Associate will not assume any obligations of Covered Entity under the Privacy Rule. To the extent that Business Associate is to carry out any of Covered Entity’s obligations under the Privacy Rule as expressly provided in the Underlying Agreement or this BAA, Business Associate will comply with the requirements of the Privacy Rule that apply to Covered Entity in the performance of such obligations.
Reporting of Improper Use or Disclosure, Security Incident, or Breach.
Business Associate will report to Covered Entity any use or disclosure of PHI not permitted under this BAA, Breach of Unsecured PHI, or any Security Incident, without unreasonable delay, and in any event no more than thirty (30) days following discovery; provided, however, that the Parties acknowledge and agree that this Section constitutes notice by Business Associate to Covered Entity of the ongoing existence and occurrence of attempted but Unsuccessful Security Incidents (as defined below). “Unsuccessful Security Incidents” will include, but not be limited to, pings and other broadcast attacks on Business Associate’s firewall, port scans, unsuccessful log-on attempts, denials of service, and any combination of the above, so long as no such incident results in unauthorized access, use, or disclosure of PHI.
Business Associate’s notification to Covered Entity of a Breach will include: (i) the identification of each individual whose Unsecured PHI has been, or is reasonably believed by Business Associate to have been, accessed, acquired, or disclosed during the Breach; and (ii) any particulars regarding the Breach that Covered Entity would need to include in its notification, as such particulars are identified in 45 C.F.R. § 164.404.
A Security Incident, for the purpose of this Section 3.3, does not include attempted or successful unauthorized access, use, disclosure, modification, or destruction of information or interference with Business Associate’s corporate information system (“non-PHI Information System”), as defined by Business Associate’s internal policies and procedures.
Subcontractors. In accordance with 45 C.F.R. § 164.502(e)(1)(ii) and 45 C.F.R. § 164.308(b)(2), as applicable, Business Associate will enter into a written agreement with any Subcontractor that creates, receives, maintains, or transmits PHI on behalf of Business Associate for services provided to Covered Entity, providing that the Subcontractor agrees to restrictions and conditions that are substantially similar to those that apply through this BAA to Business Associate with respect to such PHI. As part of this agreement, Business Associate will require any Subcontractor to whom it provides PHI to implement reasonable and appropriate safeguards to protect the PHI.
Access to PHI. The Parties do not intend for Business Associate to maintain any PHI in a Designated Record Set for Covered Entity. To the extent Business Associate possesses PHI in a Designated Record Set, Business Associate agrees to make such information available to Covered Entity pursuant to 45 C.F.R. § 164.524 and 42 U.S.C. § 17935(e) within ten (10) business days of Business Associate’s receipt of a written request from Covered Entity; provided, however, that Business Associate is not required to provide such access where the PHI contained in a Designated Record Set is duplicative of the PHI contained in a Designated Record Set possessed by Covered Entity. If an Individual makes a request for access pursuant to 45 C.F.R. § 164.524 directly to Business Associate, or inquiries about his or her right to access, Business Associate will either forward such request to Covered Entity or direct the Individual to Covered Entity.
Amendment of PHI. The Parties do not intend for Business Associate to maintain any PHI in a Designated Record Set for Covered Entity. To the extent Business Associate possesses PHI in a Designated Record Set, Business Associate agrees to make such information available to Covered Entity for amendment pursuant to 45 C.F.R. § 164.526 within twenty (20) business days of Business Associate’s receipt of a written request from Covered Entity. If an Individual submits a written request for amendment pursuant to 45 C.F.R. § 164.526 directly to Business Associate, or inquiries about his or her right to amendment, Business Associate will either forward such request to Covered Entity or direct the Individual to Covered Entity.
Documentation of Disclosures of PHI. Business Associate agrees to document such disclosures of PHI and information related to such disclosures as would be required for Covered Entity to respond to a request by an Individual for an accounting of disclosures of PHI in accordance with 45 C.F.R. § 164.528. Business Associate will document, at a minimum, the following information (“Disclosure Information”): (a) the date of the disclosure; (b) the name and, if known, the address of the recipient of the PHI; (c) a brief description of the PHI disclosed; (d) the purpose of the disclosure that includes an explanation of the basis for such disclosure; and (e) any additional information required under the HITECH Act and any implementing regulations.
Accounting of Disclosures of PHI. Business Associate agrees to provide to Covered Entity, within twenty (20) business days of Business Associate’s receipt of a written request from Covered Entity, information collected in accordance with Section 3.7 of this BAA, to permit Covered Entity to respond to a request by an Individual for an accounting of disclosures of PHI in accordance with 45 C.F.R. § 164.528 and 42 U.S.C. § 17935(c). If the Individual submits a written request for an accounting of disclosures of PHI pursuant to 45 C.F.R. § 164.528 directly to Business Associate, or inquiries about his or her right to an accounting, Business Associate will direct the Individual to Covered Entity.
Government Access to Records. Business Associate will make its internal practices, books, and records relating to the use and disclosure of PHI received from or created or received by Business Associate on behalf of, Covered Entity available to the Secretary for purposes of the Secretary determining Covered Entity’s compliance with the Privacy Rule and the Security Rule.
Mitigation. To the extent reasonable and practicable, Business Associate will cooperate with Covered Entity’s efforts, at Business Associate’s expense, to mitigate a harmful effect that is known to Business Associate of a use of disclosure of PHI by Business Associate that is not permitted by this BAA. Business Associate shall reasonably cooperate with Covered Entity’s investigation, analysis, notification, and mitigation activities, at Covered Entity’s expense, if it is determined that the source of the Breach or Security Incident is Covered Entity.
Minimum Necessary. Business Associate will request, use, and disclose the minimum amount of PHI necessary to accomplish the purpose of the request, use, or disclosure, in accordance with 45 C.F.R § 164.514(d), and any amendments thereto.
4. Obligations of Covered Entity
Notice of Privacy Practices. Covered Entity will notify Business Associate of any limitation(s) in its notice of privacy practices in accordance with 45 C.F.R § 164.520, to the extent that such limitation may affect Business Associate’s use or disclosure of PHI. Covered Entity will provide such notice no later than fifteen (15) days prior to the effective date of the limitation.
Notification of Changes Regarding Individual Permission. Covered Entity will obtain any consent or authorization that may be required by the Privacy Rule, or applicable state law, prior to furnishing Business Associate with PHI. Covered Entity will notify Business Associate of any changes in, or revocation of, permission by an Individual to use or disclose PHI, to the extent that such changes may affect Business Associate’s use or disclosure of PHI. Covered Entity will provide such notice no later than fifteen (15) days prior to the effective date of the change.
Notification of Restrictions to Use or Disclosure of PHI. Covered Entity will notify Business Associate of any restriction to the use or disclosure of PHI that Covered Entity has agreed to in accordance with 45 C.F.R. § 164.522, to the extent that such restriction may affect Business Associate’s use or disclosure of PHI. Covered Entity will provide such notice no later than (15) days prior to the effective date of the restriction. If Business Associate reasonably believes that any restriction agreed to by Covered Entity pursuant to this Section may materially impair Business Associate’s ability to perform its obligations under the Underlying Agreement of this BAA, the Parties will mutually agree upon any necessary modification of Business Associate’s obligations under such agreements.
Permissible Requests by Covered Entity. Covered Entity will not request Business Associate to use or disclose PHI in any manner that would not be permissible under the Privacy Rule, the Security Rule, or the HITECH Act if done by Covered Entity, except as permitted pursuant to the provisions of Sections 2.2, 2.3, and 2.4 of this BAA.
Minimum Necessary Disclosure. The Covered Entity shall provide to Business Associate only the “minimum necessary” PHI (as described in 45 C.F.R. § 164.502(b)) required for Business Associate to perform its obligations under the Underlying Agreement.
5. Term and Termination
Term. The term of this BAA will commence as of the Effective Date and will terminate upon the effective date of termination of the Underlying Agreement.
Termination for Cause. Upon either Party’s knowledge of a material breach by the other Party of this BAA, such Party may terminate this BAA immediately if cure is not possible. Otherwise, the non-breaching Party will provide written notice to the breaching Party detailing the nature of the breach and providing an opportunity to cure the breach with thirty (30) business days. Upon the expiration of such thirty (30) day cure period, the non-breaching Party may terminate this BAA if the breaching party does not cure the breach or if cure is not possible. A Party’s option to have cured a material breach of this BAA will not be construed as a waiver of any other rights such Party has under this BAA, by operation of law or in equity.
Effect of Termination. Except as provided in Section 5.2, upon termination of the Underlying Agreement or this BAA for any reason, Business Associate will return or destroy all PHI received from Covered Entity or created or received by Business Associate on behalf of Covered Entity, at Covered Entity’s expense, and will retain no copies of the PHI. This provision will apply to PHI that is in the possession of Subcontractors or agents of Business Associate.
If it is not feasible for Business Associate to return or destroy the PHI upon termination of this BAA (e.g., because ePHI has been integrated into a database maintained by Business Associate and removal from the database is burdensome or impossible, or PHI has been aggregated with other PHI in a manner that makes it infeasible to extract PHI received from Covered Entity), Business Associate will: (a) extend the protections of this BAA to such PHI and (b) limit further uses and disclosures of such PHI to those purposes that make the return or destruction infeasible, for so long as Business Associate maintains such PHI.
6. General Terms
Cooperation in Investigations. The Parties acknowledge that certain breaches or violations of this BAA may result in litigation or investigations pursued by federal or state governmental authorities of the United States resulting in civil liability or criminal penalties. Each Party will cooperate in good faith in all respects with the other Party in connection with any request by a federal or state governmental authority for additional information and documents or any governmental investigation, complaint, action or other inquiry.
Notices. Notices under this BAA shall be given in accordance with the Notices provision of the Underlying Agreement, including its email delivery and effectiveness provisions. Reports required under Section 3.3 shall be sent to Covered Entity’s designated privacy or security contact, or, if none has been designated, its notice contact under the Underlying Agreement, within the applicable reporting period. Courier or postal confirmation is not required.
Governing Law. This BAA is governed by, and will be construed in accordance with, the laws of the State that govern the Underlying Agreement. Any action by either Party arising out of this BAA must be commenced within two (2) years after the cause of action accrued, to the extent permitted by applicable law. This period supersedes any inconsistent contractual limitation period for actions arising out of this BAA and does not limit governmental enforcement or any rights or obligations that cannot lawfully be limited by contract.
Amendment. This BAA may be amended or supplemented only by a writing that refers explicitly to this BAA and that is signed by both Parties. The Parties agree to amend this BAA as required to comply with any changes in laws, rules, or regulations that affect the privacy and security of PHI and the Business Associate’s duties under the Underlying Agreement or this BAA.
Assignment. Neither Party will assign this BAA without the prior written consent of the other Party, which will not be unreasonably withheld.
Waiver. No delay or failure of either Party to exercise any right or remedy available under this BAA, at law, or in equity will act as a waiver of such right or remedy, and any waiver will not waive any subsequent right, obligation, or default.
Order of Precedence. Any ambiguity in this BAA shall be resolved to permit compliance with the HIPAA Rules. This BAA controls any conflict concerning privacy, security, use or disclosure of PHI, breach reporting, and PHI return or destruction, including a conflict with Schedule C. Schedule C controls clinical supervision and operational matters unrelated to the foregoing PHI obligations, as provided in the Underlying Agreement. The main Services Agreement controls all other general commercial terms, including remedies, limitations of liability, warranties, governing law, venue, and relationship of the Parties, except to the extent their application would prevent compliance with mandatory HIPAA obligations.
Severability. If any provision of this BAA is determined by a court of competent jurisdiction to be invalid, void, or unenforceable, the remaining provisions of this BAA will continue in full force and effect.
Survival. The rights and obligations contained in Sections 3.3 (Reporting of Improper Use or Disclosure, Security Incident, or Breach), 3.8 (Accounting of Disclosures of PHI), 3.9 (Government Access to Records), 3.10 (Mitigation), 5.3 (Effect of Termination), and 6 (General Terms) will survive the termination of this BAA.
No Third-Party Beneficiaries. Nothing express or implied in this BAA is intended to confer, nor will anything in this BAA confer, upon any person other than Covered Entity, Business Associate, or their respective successors or permitted assigns, any rights, remedies, obligations, or liabilities whatsoever.
Counterparts. This BAA may be executed in counterparts, each of which will be deemed an original, and all of which will constitute one binding agreement and may be delivered by electronic mail or fax.
[End of Schedule B]
This Schedule C forms part of the DayaMed Services Agreement between Daya Medicals, Inc. (“DayaMed”) and the customer identified in the applicable Order Form (“Customer”). It takes effect on the Effective Date of the Agreement and applies only to the Clinical Services selected in the Order Form and described in Schedule A. Capitalized terms not defined here have the meanings assigned in the Agreement. References to the Agreement include its Order Form and schedules.
1. Integration and controlling terms
This Schedule establishes the clinical operating and supervision framework for DayaMed personnel furnishing selected Clinical Services under Customer’s designated practitioners. It does not establish medical billing or revenue cycle services. Any optional Medical Billing Services are governed solely by the applicable provisions of the main Services Agreement and Order Form. This Schedule is incorporated into the Agreement and requires no separate signature or term.
For conflicts concerning clinical supervision, personnel qualifications, practitioner attribution, clinical documentation, or escalation, this Schedule controls over inconsistent provisions in the Agreement or Schedule A. Schedule B controls privacy, security, and Protected Health Information matters. All commercial terms and optional Medical Billing Services remain governed by the main Services Agreement and applicable Order Form. No provision of this Schedule waives applicable law, licensing rules, or service-specific supervision requirements.
2. Definitions and service-specific requirements
“Clinical Services” means the clinical support and care-management activities expressly selected in the Order Form and described in Schedule A. This Schedule does not add services or expand the scope of a selected program.
“Supervising Practitioner” means a physician or other qualified healthcare practitioner designated by Customer who is legally permitted to supervise the applicable service and satisfies the applicable payer requirements. “DayaMed Clinical Personnel” means nurses, medical assistants, care managers, care coordinators, or other appropriately qualified personnel assigned by DayaMed.
“General Supervision” means overall direction and control by the applicable Supervising Practitioner without requiring that practitioner’s physical presence during performance, only to the extent permitted for the particular service. Any higher supervision, personal-performance, ordering, delegation, or collaboration requirement imposed by law, licensing rules, or payer policy continues to apply.
General supervision shall not be assumed to apply to every service. The Parties shall confirm the required supervision and personnel qualifications before implementation and as requirements change. Where applicable incident-to rules govern performance of a service, the actual personnel arrangement and clinical work must satisfy those rules. This Schedule does not by itself establish personnel qualifications or permit a lower level of supervision than required.
3. Organizational supervision and patient attribution
Customer authorizes DayaMed Clinical Personnel to furnish selected Clinical Services under Customer-approved protocols and the supervision required for each service. This is an organizational framework and does not establish an exclusive relationship between any particular practitioner and any particular DayaMed staff member.
Customer may designate multiple Supervising Practitioners through its EHR, patient roster, clinical assignment records, department, service line, practice location, or another agreed written or electronic method. Customer shall maintain sufficient records to identify the practitioner responsible for each patient and service when required, including the effective dates of assignment changes.
Customer shall ensure that designated practitioners are qualified and authorized to fulfill their responsibilities and that coverage continues during absences or assignment changes. Roster changes do not require an amendment or separate practitioner signature under this Schedule. Any separate arrangement required by applicable law or payer rules must nevertheless be completed.
A Customer signatory binds only the legal entity or entities it is authorized to bind. Separately organized affiliated practices must be expressly included through an authorized joinder, Order Form, or other written arrangement where necessary.
4. Staffing, substitution, and personnel independence
DayaMed may assign, reassign, substitute, or replace its Clinical Personnel and use a team-based staffing model without amending the Agreement or obtaining a separate signature for each staffing change. Replacement personnel must satisfy applicable qualifications and Customer’s reasonable, previously communicated credentialing and access requirements before performing the affected services.
DayaMed shall maintain appropriate records of licensure and certifications where required, training, competency, and applicable exclusion and sanctions screening. No person may perform work outside that person’s lawful scope of practice. Upon reasonable request, DayaMed shall provide relevant qualification documentation and a current roster of personnel assigned to Customer.
DayaMed remains responsible for personnel compensation, scheduling, and employment or contracting obligations. Supervision by a Customer practitioner does not, by itself, make DayaMed personnel employees of Customer. Customer may request removal of personnel for a documented qualification, compliance, or patient-safety concern; the Parties shall coordinate appropriate replacement and continuity of care.
5. Customer and practitioner responsibilities
Customer shall determine patient eligibility and medical necessity; provide required service orders; establish, approve, or oversee care plans as applicable; and maintain the practitioner involvement required by the selected program. DayaMed may assist with care-plan development and documentation, but cannot independently approve clinical decisions reserved to a qualified practitioner.
Customer and its practitioners retain responsibility for diagnosis, prescribing, treatment decisions, and any service component that must be personally furnished. They shall provide overall clinical direction, review information when required, and address escalations requiring practitioner judgment.
Customer shall designate a Clinical Contact and backup coverage during agreed clinical operating hours, provide current escalation contacts and response arrangements, and fulfill any program-specific after-hours access requirements described in Schedule A. Practitioner reassignment shall not interrupt required supervision or coverage.
6. DayaMed responsibilities and approved protocols
DayaMed shall provide qualified personnel, train them on Customer-approved workflows, maintain appropriate service records, communicate material clinical concerns, and follow the agreed escalation procedures. DayaMed is responsible for its own performance and personnel conduct subject to the Agreement.
Customer retains clinical authority over protocols for its patients. Approved workflows, monitoring parameters, escalation thresholds, and program procedures may be maintained electronically outside this Schedule. DayaMed personnel may perform routine actions within approved protocols and lawful scope without obtaining separate approval for each action, unless law, payer requirements, the protocol, or the patient’s condition requires practitioner involvement.
Personnel shall not diagnose, prescribe, change prescriptions, or independently modify treatment plans where those actions require practitioner authority. Routine workflow updates do not amend contractual scope, pricing, or risk allocation; those changes require the written agreement prescribed by the Agreement.
7. Escalation and emergency response
The Parties shall establish and maintain a documented escalation process before starting the affected Clinical Services. It shall identify program-specific thresholds, designated contacts, backup contacts, expected response times, after-hours arrangements, and steps to take if a contact cannot be reached. Agreed operating hours shall be consistent with Schedule A.
Routine findings within approved parameters may be documented and managed under the approved workflow. Non-emergent findings exceeding a threshold or requiring practitioner judgment shall be escalated to Customer’s designated clinical team. Urgent findings shall trigger prompt contact with the designated practitioner or backup resource and the agreed urgent-care workflow.
For apparent emergencies, personnel shall instruct or facilitate appropriate emergency response consistent with their training and notify Customer as appropriate. Personnel need not await a practitioner response before arranging emergency services when reasonably indicated. Monitoring Services are not an emergency-response system and do not imply continuous emergency surveillance.
8. Systems access and clinical documentation
Customer shall provide secure, individual, role-appropriate access credentials where its EHR or other systems are used. Personnel shall not share credentials. Access shall be limited to information reasonably necessary for authorized services, consistent with Schedule B and applicable law.
The Parties shall designate the system of record before implementation. Documentation may be maintained in Customer’s EHR, the DayaMed platform, or another mutually agreed system, with timely authorized access or transfer to Customer. Direct entry into Customer’s EHR is required only if expressly agreed or otherwise required.
Unless a different standard is agreed in writing or a shorter period is required, DayaMed shall document completed interactions and activities contemporaneously or within 24 hours. Urgent and emergency concerns shall be communicated without waiting for completion of routine documentation. System outages shall be handled through an approved contingency process with subsequent reconciliation.
Records shall identify the patient, service date, personnel performing the service, relevant activity and findings, applicable care-plan information, time where required, and escalations. Entries and corrections shall preserve authorship and an appropriate audit trail. This 24-hour standard is a contractual operating requirement, not a representation that every payer mandates that interval.
9. Patient consent and enrollment
Consistent with the Agreement, DayaMed shall obtain required service consent in a Customer-approved format unless the Parties expressly assign that function otherwise in writing. Before initiating services that require consent, the responsible Party shall obtain and document the required consent, and DayaMed shall verify that the record is available in the designated system.
The responsible Party shall explain the selected clinical program and obtain the consent disclosures required for that program, including the patient’s right to discontinue services. Consent may be verbal or written where permitted. Any additional required financial disclosures remain governed by applicable requirements and Customer-approved consent procedures. This Schedule does not create a universal requirement for a signed patient form.
The Parties shall communicate withdrawal of consent, loss of eligibility, duplicate enrollment concerns, and other reasons for discontinuation promptly, and coordinate unenrollment under the Agreement.
10. Quality review, privacy, and records
The Parties shall cooperate in reasonable reviews of documentation, qualifications, escalation performance, and clinical service delivery relevant to the selected Services, subject to confidentiality and privilege protections. Each Party shall maintain records for the periods required by applicable law, payer requirements, and the Agreement.
Schedule B governs use and disclosure of Protected Health Information, safeguards, incident reporting, subcontractor obligations, and return or destruction of information. This Schedule does not create a separate BAA or replace the existing BAA.
Insurance, indemnification, and liability obligations remain governed by the main Services Agreement; this Schedule creates no separate commercial risk allocation.
11. Changes in requirements, suspension, and transition
Each Party shall comply with applicable law, licensing requirements, and payer rules governing its responsibilities. If a change materially affects the legality or permissible delivery of a service, the Parties shall modify the affected workflow before continuing that service.
Either Party may promptly suspend an affected clinical activity when continuation would reasonably create a material patient-safety, licensing, or compliance risk, with notice to the other Party as soon as practicable. Suspension shall be limited to the affected activity where feasible, and the Parties shall coordinate appropriate patient coverage or transition. This provision does not create a general termination-for-convenience right.
Upon expiration, termination, or discontinuation of an affected Service, the Parties shall coordinate an orderly transition of active patients and necessary records, consistent with Schedule B and applicable record-retention requirements. The Agreement governs termination rights.
12. Operational records and execution
The Parties shall maintain operational records identifying the selected programs; system of record and transfer method; supervising practitioner assignments; clinical and backup contacts; operating hours; escalation thresholds and response arrangements; and approved protocols. These records may be approved and updated through agreed written or electronic channels without separate contract signatures, except where law or payer requirements mandate otherwise.
This Schedule is accepted through execution of the Order Form or Agreement that expressly incorporates it. No separate signatures are required on this Schedule. If added after the Agreement has already been executed, incorporation requires a written amendment signed by the Parties as required by the Agreement.
[End of Schedule C]