NOTE 1 – BASIS OF PRESENTATION AND RECENTLY ISSUED ACCOUNTING PRONOUNCEMENTS

The accompanying unaudited interim Condensed Consolidated Financial Statements of CareView Communications, Inc. (“CareView”, the “Company”, “we”, “us” or “our”) have been prepared in accordance with generally accepted accounting principles in the United States of America (“GAAP”) for interim financial information and with the instructions to Form 10-Q. Accordingly, they do not include all of the information and footnotes required by GAAP for complete financial statements. In the opinion of management, such financial statements include all adjustments (consisting solely of normal recurring adjustments) necessary for the fair statement of the financial information included herein in accordance with GAAP and the rules and regulations of the Securities and Exchange Commission (the “SEC”). The balance sheet at December 31, 2025 has been derived from the audited Consolidated Financial Statements at that date but does not include all of the information and footnotes required by GAAP for complete financial statements. The preparation of financial statements in conformity with GAAP requires management to make estimates and assumptions that affect the reported amounts of assets and liabilities and the disclosure of contingent assets and liabilities at the date of the financial statements and the reported amounts of revenue and expenses during the period. Actual results could differ from those estimates. Results of operations for interim periods are not necessarily indicative of results for the full year. The accompanying unaudited Condensed Consolidated Financial Statements should be read in conjunction with the audited Consolidated Financial Statements and related notes included in our Annual Report on Form 10-K for the year ended December 31, 2025 as filed with the SEC on March 30, 2026.

Revenue Recognition

We recognize revenue in accordance with Accounting Standards Codification (“ASC”) Topic 606 (“ASC 606”). For our subscription service contracts, we have employed the practical expedient discussed in ASC 606-10-55-18 related to invoicing as we have the right to consideration from our customers in the amount that corresponds directly with the value to the customer of our performance completed to date and therefore, we recognize revenue upon invoicing as further discussed below.

In accordance with ASC 606, revenue is recognized when a customer obtains control of promised goods or services. The amount of revenue recognized reflects the consideration to which we expect to be entitled to receive in exchange for these goods or services. The provisions of ASC 606 include a five-step process by which we determine revenue recognition, depicting the transfer of goods or services to customers in amounts reflecting the payment to which we expect to be entitled in exchange for those goods or services. ASC 606 requires us to apply the following steps: (1) identify the contract with the customer; (2) identify the performance obligations in the contract; (3) determine the transaction price; (4) allocate the transaction price to the performance obligations in the contract; and (5) recognize revenue when, or as, we satisfy the performance obligation. For those customers for which we are required to collect sales taxes, we record such sales taxes on a net basis which has no effect on the amount of revenue or expenses recognized as the sales taxes are a flow through to the taxing authority.

We enter into contracts with customers that may provide multiple combinations of our products, software solutions, and other related services, which are generally capable of being distinct and accounted for as separate performance obligations. Performance obligations that are not distinct at contract inception are combined.

Customer contract fulfillment typically involves multiple procurement promises, which may include various equipment, software subscription, project-related installation and training services, and support. We allocate the transaction price to each performance obligation based on estimated relative standalone selling price. Revenue is then recognized for each performance obligation upon transferring control of the hardware, software, and services to the customer and in an amount that reflects the consideration we expect to receive and the estimated benefit the customer receives over the term of the contract.

Generally, we recognize revenue under each of our performance obligations as follows:

	●	Subscription services – We recognize subscription revenues monthly over the contracted license period.
	●	Equipment packages – We recognize equipment revenues when control of the devices has been transferred to the client (“point in time”).
	●	Software bundle and related services related to sales-based contracts – We recognize our software subscription, installation, training, and other services on a straight-line basis over the estimated contracted license period (“over time”).

The Company earns sales-based contract revenue from services rendered under specific agreements, which hinge on a third-party reseller who possesses the exclusive authority to engage directly with veteran-owned hospitals. Evaluating the Company’s role in these contracts necessitates assessing whether it functions as the principal or agent, a determination that involves analyzing the extent of control the Company wields over the contracts.

Following its assessment, the Company reports revenue from services provided under such contracts on a gross basis. This decision is justified by the Company's primary responsibility to fulfill the contractual obligations, including delivery and installation of equipment and software, training, and its control over other services within the contract period. Furthermore, the Company directly sets the contract price with its customers based on the services outlined in the statement of work. As the Company is responsible for fulling this promise and maintains control, the Company is acting as the principal.

Our sales-based contract payment arrangements with our customers typically include an initial equipment payment due upon signing of the contract and subsequent payments when certain performance obligations are completed. Customer payments received in advance of satisfaction of related performance obligations are deferred as contract liabilities. These amounts are recorded as “deferred revenue” in our Condensed Consolidated Balance Sheets and recognized into revenues as either a point in time or over time.

During the three months ended March 31, 2026 and 2025, sales-based deferred contract liability recognized as revenue totaled $1,160,073 and $1,149,315, respectively. The table below details the sales-based contract liability activity during the three months ended March 31, 2026 and 2025.

As of March 31, 2026, the aggregate amount of deferred revenue from subscription-based contracts and sales-based contracts allocated to performance obligations that are unsatisfied or partially satisfied is $2,618,960 and will be recognized into revenue over time as follows:

We defer and capitalize all costs associated with the installation of the CareView System into a healthcare facility until the CareView System is fully operational and accepted by the healthcare facility. Installation costs are specifically identifiable based on the amounts we are charged from third party installers or directly identifiable internal labor hours incurred for each installation. Upon acceptance, the associated costs are expensed on a straight-line basis over the life of the contract with the healthcare facility. These costs are included in network operations on the accompanying Condensed Consolidated Statements of Operations.

The table below details the activity in these deferred installation costs during the periods ended March 31, 2026 and 2025, included in other assets in the accompanying unaudited Condensed Consolidated Balance Sheets.

Contracts with our customers are typically structured similarly and include various combinations of our products, software solutions, and related services. Determining whether the various contract promises are considered distinct performance obligations that should be accounted for separately versus together may require significant judgment.

The contract transaction price is allocated to distinct performance obligations using the estimated standalone selling price. We determine the standalone selling price through maximizing observable inputs such as standalone sales, competitor standalone sales, or substantive renewal prices charged to customers when they exist. In instances where the standalone selling price is not observable, we utilize an estimate of standalone selling price. Such estimates are derived from various methods that include cost plus margin, and historical pricing practices. Judgment may be required to determine standalone selling prices for each performance obligation and whether it depicts the amount we expect to receive in exchange for the related good or service.

Contract modifications occur when we and our customers agree to modify existing customer contracts to change the scope or price (or both) of the contract or when a customer terminates some, or all, of the existing services provided by us. When a contract modification occurs, it requires us to exercise judgment to determine if the modification should be accounted for as a separate contract, the termination of the original contract and creation of a new contract, a cumulative catch-up adjustment to the original contract, or a combination.

Contracts with our customers include a limited warranty on our products covering materials, workmanship, or design for the duration of the contract. We do not offer paid additional extended or lifetime warranty packages. We determined that limited warranty in our contract is not a distinct performance obligation. We do not believe our estimates of warranty costs to be significant to our determination of revenue recognition, and therefore, did not reserve for warranty costs.

The Company has an operating lease primarily consisting of office space with a remaining lease term of 57 months. At the lease commencement date, an operating lease liability and related operating lease asset are recognized. The operating lease liabilities are calculated using the present value of lease payments. The discount rate used is either the rate implicit in the lease, when known, or our estimated incremental borrowing rate. Operating lease assets are valued based on the initial operating lease liabilities plus any prepaid rent and direct costs from executing the leases.

We calculate earnings per share (“EPS”) in accordance with GAAP, which requires the computation and disclosure of two EPS amounts, basic and diluted. Basic EPS is computed based on the weighted average number of common shares outstanding during the period. Diluted EPS is computed based on the weighted average number of common shares outstanding plus all potentially dilutive common shares outstanding during the period under the treasury stock method. Such potential dilutive common shares consist of stock options, and warrants to purchase our Common Stock (the “Warrants”). Potential common shares totaling 66,676,835 and 66,975,835 on March 31, 2026 and 2025, respectively, have been excluded from the diluted earnings per share calculation as they are anti-dilutive due to our reported net loss. For 2026, the 66,676,835 potential common shares consist of 65,426,835 stock options and 1,250,000 warrants, compared to 66,975,835 potential common shares in 2025, which consisted of 65,725,835 stock options and 1,250,000 warrants.

In December 2023, the FASB issued ASU 2023-09, Income Taxes (Topic 740): Improvements to Income Tax Disclosures. This update will improve the transparency and usefulness of income tax disclosures. Investors, lenders, and creditors have indicated that current disclosures do not provide enough detailed information to assess how a company's operations, tax risks, and planning affect its tax rate and future cash flows. The requirements take effect for public business entities for fiscal years beginning after December 15, 2024. The Company adopted this standard in its 2025 annual period on a prospective basis. The adoption enhances the Company’s income tax disclosures by increasing detail and transparency, but did not affect the Company’s financial position, results of operations, or cash flows.

In November 2024, the FASB issued ASU No. 2024-04, “Debt with Conversion and Other Options (Subtopic 470-20): Induced Conversions of Convertible Debt Instruments,” which clarifies the criteria for determining when a settlement of convertible debt should be accounted for as an induced conversion. The guidance applies only to conversions involving the full issuance of equity securities as originally specified in the debt terms and includes additional clarifications to aid in application. The amendments in this update are effective for all entities for annual reporting periods beginning after December 15, 2025, and interim reporting periods within those annual reporting periods. The Company adopted this standard on January 1, 2026. The adoption of this guidance did not have a material impact on the Company’s Condensed Consolidated Financial Statements, as the Company has no outstanding convertible debt instruments.

In July 2025, the FASB issued ASU 2025-05, "Financial Instruments—Credit Losses (Topic 326): Measurement of Credit Losses for Accounts Receivable and Contract Assets," which amends how entities estimate expected credit losses for current accounts receivable and current contract assets arising from revenue contracts under ASC 606. A reduction in the need for extensive forecasting has been established and allows all entities to assume that conditions will persist at balance sheet date for the remaining life of those current assets. The amendments in this update are effective for all entities for annual reporting periods beginning after December 15, 2025, and interim periods within those annual reporting periods. Upon adoption, the standard did not have a material impact on the Company's financial statements.

There was no impact on our Condensed Consolidated Financial Statements from recently adopted accounting standards.

In October 2023, the FASB issued ASU No. 2023-06, which incorporates 14 of the 27 SEC disclosures identified in SEC Release No. 33-10532 (issued August 17, 2018). This ASU updates disclosure and presentation requirements across various Codification Topics and applies to all entities within the scope of those Topics, unless specified otherwise. The amendments are to be applied prospectively. For public business entities, each amendment becomes effective when the related SEC disclosure is removed from Regulation S-X or S-K; early adoption is not permitted. The Company has evaluated ASU No. 2023-06 and does not expect it to impact its Condensed Consolidated Financial Statements.

In November 2024, the FASB issued ASU 2024-03, Income Statement - Reporting Comprehensive Income - Expense Disaggregation Disclosures (Subtopic 220-40). This update will enhance disclosures about public business entity’s expenses, responding to investor requests for more detailed information on components such as inventory purchases, employee compensation, depreciation, amortization, and depletion within commonly presented expense captions (e.g., cost of sales, SG&A, and R&D). These amendments are expected to provide investors with a clearer understanding of an entity’s expenses, helping them assess performance, forecast future expenses, and evaluate cash flow prospects. The effective date for these amendments, as clarified by ASU 2025-01, are for annual reporting periods beginning after December 15, 2026, and interim reporting periods within annual reporting periods beginning after December 15, 2027. The standard can be applied either prospectively or retrospectively. We are currently assessing adoption timing and the effect that the updated standard will have on our financial statement disclosures.

In September 2025, the FASB issued ASU 2025-06, "Intangibles—Goodwill and Other—Internal-Use Software (Subtopic 350-40): Targeted Improvements to the Accounting for Internal-Use Software." The update eliminates all references to "development stages", so entities are no longer required to wait for a specific application development stage before capitalizing costs. The two key criteria for when capitalization of internal-use software costs may begin are when Management has authorized and committed to funding the software project, and it is probable that the project will be completed and the software will be used to perform the intended function. The amendments are effective for all entities for annual reporting periods beginning after December 15, 2027, and interim reporting periods within those annual reporting periods. Early adoption is permitted as of the beginning of an annual reporting period. Management is currently assessing the potential effects on our financial statements and considering the possibility of early adoption.

There have been no material changes to our significant accounting policies as summarized in NOTE 2 of our Condensed Consolidated Financial Statements for the period ended March 31, 2026. We do not expect that the adoption of any recent accounting pronouncements will have a material impact on our accompanying Condensed Consolidated Financial Statements.