XML 20 R10.htm IDEA: XBRL DOCUMENT
v3.24.1.1.u2

REVENUE RECOGNITION | 3 Months Ended
--- | ---
Mar. 31, 2024
Revenue from Contract with Customer [Abstract] |
REVENUE RECOGNITION | REVENUE RECOGNITION Revenue is recognized upon transfer of control of promised products or services to clients in an amount that reflects the consideration we expect to receive in exchange for those products and services. We enter into contracts that can include various combinations of products and services, which are generally distinct and accounted for as separate performance obligations. The Company employs the 5-step revenue recognition model under ASC 606, Revenue from Contracts with Customers, to: (1) identify the contract with the client, (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) the entity satisfies a performance obligation. Revenue is recognized net of shipping charges and any taxes collected from clients, which are subsequently remitted to governmental authorities. •Revenue Cycle Management Our revenue cycle management (“RCM”) business unit provides an array of business processing services (“BPS'’) consisting of accounts receivable management, private pay services, insurance services, medical coding, electronic billing, statement processing, payroll processing, and contract management. Fees are recognized over the period of the client contractual relationship as the services are performed based on the stand-alone selling price (“SSP”), net of discounts. SSP for BPS services is determined based on observable stand-alone selling prices. Fees for many of these services are invoiced, and revenue recognized accordingly, based on the volume of transactions or a percentage of client accounts receivable collections. Payment is due monthly for BPS with certain amounts varying based on utilization and/or volumes. Our RCM business unit also provides professional IT services. Revenue from professional IT services is recognized as the services are performed based on SSP, which is determined by observable stand-alone selling prices. Payment is due monthly as services are performed. Lastly, our RCM business unit also provides certain software solutions and related support under Software as a Service (“SaaS”) arrangements and time-based software licenses. Revenue from SaaS arrangements is recognized in a manner consistent with SaaS arrangements for electronic health records (“EHR”) software, as discussed below. Revenue from time-based software licenses is recognized upon delivery to the client (“point in time”) and revenue from non-license components (i.e., support) is recognized ratably over the respective contract term (“over time”). SSP for time-based licenses is determined using the residual approach, while the non-license component is based on cost plus reasonable margin. •Electronic Health Records The Company enters into contractual obligations to sell perpetual software licenses, installation, conversion, and related training services, software application support, hardware, and hardware maintenance services to acute care community hospitals and post-acute providers. •Non-recurring Revenues •Perpetual software licenses and installation, conversion, and related training services are not considered separate and distinct performance obligations due to the proprietary nature of our software and are, therefore, accounted for as a single performance obligation on a module-by-module basis. Revenue is recognized as each module's implementation is completed based on the module's SSP, net of discounts. We determine each module's SSP using the residual method. Fees for licenses and installation, conversion, and related training services are typically due in three installments: (1) at placement of order, (2) upon installation of software and commencement of training, and (3) upon satisfactory completion of monthly accounting cycle or end-of-month operation by application and as applicable for each application. Often, short-term and/or long-term financing arrangements are provided for software implementations; refer to Note 11 - Financing Receivables for further information. EHR implementations include a system warranty that terminates thirty days from the software go-live date, the date which the client begins using the system in a live environment. •Hardware revenue is recognized separately from software licenses at the point in time it is delivered to the client. The SSP of hardware is cost plus a reasonable margin and revenue is recognized on a gross basis. Payment is generally due upon delivery of the hardware to the client. Standard manufacturer warranties apply to hardware. •Recurring Revenues •Software application support and hardware maintenance services sold with software licenses and hardware are separate and distinct performance obligations. Revenue for support and maintenance services is recognized based on SSP, which is the renewal price, ratably over the life of the contract, which is generally three to five years. Payment is due monthly for support and maintenance services provided. •Subscriptions to third-party content revenue is recognized as a separate performance obligation ratably over the subscription term based on SSP, which is cost plus a reasonable margin, and revenue is recognized on a gross basis. Payment is due monthly for subscriptions to third party content. •SaaS arrangements for EHR software and related conversion and training services are considered a single performance obligation. Revenue is recognized on a monthly basis as the SaaS service is provided to the client over the contract term. Payment is due monthly for SaaS services provided. Refer to Note 17 - Segment Reporting for further information, including revenue by client base (acute care or post-acute care) bifurcated by recurring and non-recurring revenue. •Patient Engagement The Company enters into contractual obligations to sell perpetual and term-based software licenses, implementation and customization professional services, and software application support services to a variety of healthcare organizations including hospital systems, health ministries, and government and non-profit organizations. •Non-recurring Revenues •Perpetual software licenses are sold only to one re-seller client and are considered a separate and distinct performance obligation. Revenue is recognized at the point in time perpetual licenses are delivered to the client, which occurs at the time of sale. The SSP of perpetual licenses is directly observable. Payment is generally due upon delivery of licenses. •Implementation and customization services are considered a separate and distinct performance obligation. Revenue is recognized over time based on SSP, which is generally directly observable. Payment for professional services is typically due in two installments: (1) upon signature of the agreement and (2) upon customer acceptance of the delivered services. •Recurring Revenues •Term-based software licenses are considered a separate and distinct performance obligation. Revenue is recognized based on SSP, which is directly observable, at the point in time the term-based licenses are delivered to the client or upon annual renewal. Payment is generally due upon delivery of licenses or upon annual renewal. •Software application support services sold with software licenses are separate and distinct performance obligations. The related revenues are recognized based on SSP, which is the renewal price, ratably over the life of the contract, which is generally three to five years. Payment is generally due for the full amount of annual support fees at the beginning of an annual license term. Refer to Note 17 - Segment Reporting for further information. Deferred Revenue Deferred revenue represents amounts invoiced to clients for which the services under contract have not been completed and revenue has not been recognized, including annual renewals of certain software subscriptions and customer deposits for implementations to be performed at a later date. Revenue is recognized ratably over the life of the software subscriptions as services are provided and at the point-in-time when implementations have been completed. The following table details deferred revenue for the three months ended March 31, 2024 and 2023, included in the condensed consolidated balance sheets:
(In thousands) |  |  | Three Months Ended March 31, 2024 |  | Three Months Ended March 31, 2023
Beginning balance |  |  | $ | 8,677 |  |  | $ | 11,590 |
Deferred revenue recorded |  |  | 4,360 |  |  | 6,490 |
Less deferred revenue recognized as revenue |  |  | (3,958) |  |  | (6,443) |
Ending balance |  |  | $ | 9,079 |  |  | $ | 11,637 |
The deferred revenue recorded during the three months ended March 31, 2024 and 2023 is comprised primarily of the annual renewals of certain software subscriptions billed during the first quarter of each year and deposits collected for future EHR installations. The deferred revenue recognized as revenue during the three months ended March 31, 2024 and 2023 is comprised primarily of the periodic recognition of annual renewals that were deferred until earned and deposits for future EHR installations that were earned during the period. Costs to Obtain and Fulfill a Contract with a Customer Costs to obtain a contract include the commission costs related to SaaS and RCM arrangements, which are capitalized and amortized ratably over the expected life of the customer contract. As a practical expedient, we generally recognize the incremental costs of obtaining a contract as an expense when incurred if the amortization period of the asset would have been one year or less. Costs to obtain a contract are expensed within the caption “Expenses - Sales and marketing” in the accompanying condensed consolidated statements of income. Contract fulfillment costs related to the implementation of SaaS arrangements are capitalized and amortized ratably over the expected life of the customer contract. Costs to fulfill contracts consist of the payroll costs for the implementation of SaaS arrangements, including time for training, conversions, and installation that is necessary for the software to be utilized. Contract fulfillment costs are expensed within the caption “Costs of revenue (exclusive of amortization and depreciation) - EHR” in the accompanying condensed consolidated statements of income. Costs to obtain and fulfill contracts related to SaaS and RCM arrangements are included within the “Prepaid expenses and other current assets” and "Other assets, net of current portion" line items on our condensed consolidated balance sheets as shown in the table below for the three months ended March 31, 2024 and 2023:
(In thousands) | Three Months Ended March 31, 2024 |  | Three Months Ended March 31, 2023 |  |
Beginning balance | $ | 13,115 |  |  | $ | 11,557 |  |  |
Costs to obtain and fulfill contracts capitalized | 1,703 |  |  | 1,824 |  |  |
Less costs to obtain and fulfill contracts recognized as expense | (1,884) |  |  | (1,264) |  |  |
Ending balance | $ | 12,934 |  |  | $ | 12,117 |  |  |
Remaining Performance Obligations Disclosures regarding remaining performance obligations are not considered material as the overwhelming majority of the Company's remaining performance obligations either (a) are related to contracts with an expected duration of one year or less, or (b) exhibit revenue recognition in the amount to which the Company has the right to invoice.

X
- References No definition available. + Details
Name: | us-gaap_RevenueFromContractWithCustomerAbstract
Namespace Prefix: | us-gaap_
Data Type: | xbrli:stringItemType
Balance Type: | na
Period Type: | duration

X
- Definition The entire disclosure of revenue from contract with customer to transfer good or service and to transfer nonfinancial asset. Includes, but is not limited to, disaggregation of revenue, credit loss recognized from contract with customer, judgment and change in judgment related to contract with customer, and asset recognized from cost incurred to obtain or fulfill contract with customer. Excludes insurance and lease contracts. + References Reference 1: http://www.xbrl.org/2003/role/disclosureRef -Topic 606 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 9 -Publisher FASB -URI https://asc.fasb.org//1943274/2147479806/606-10-50-9 Reference 2: http://www.xbrl.org/2003/role/disclosureRef -Topic 606 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 10 -Publisher FASB -URI https://asc.fasb.org//1943274/2147479806/606-10-50-10 Reference 3: http://www.xbrl.org/2003/role/disclosureRef -Topic 606 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 15 -Publisher FASB -URI https://asc.fasb.org//1943274/2147479806/606-10-50-15 Reference 4: http://www.xbrl.org/2003/role/disclosureRef -Topic 606 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 12 -Subparagraph (a) -Publisher FASB -URI https://asc.fasb.org//1943274/2147479806/606-10-50-12 Reference 5: http://www.xbrl.org/2003/role/disclosureRef -Topic 606 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 12 -Subparagraph (b) -Publisher FASB -URI https://asc.fasb.org//1943274/2147479806/606-10-50-12 Reference 6: http://www.xbrl.org/2003/role/disclosureRef -Topic 606 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 12 -Subparagraph (c) -Publisher FASB -URI https://asc.fasb.org//1943274/2147479806/606-10-50-12 Reference 7: http://www.xbrl.org/2003/role/disclosureRef -Topic 606 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 12 -Subparagraph (d) -Publisher FASB -URI https://asc.fasb.org//1943274/2147479806/606-10-50-12 Reference 8: http://www.xbrl.org/2003/role/disclosureRef -Topic 606 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 12 -Subparagraph (e) -Publisher FASB -URI https://asc.fasb.org//1943274/2147479806/606-10-50-12 Reference 9: http://www.xbrl.org/2003/role/disclosureRef -Topic 606 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 13 -Subparagraph (b)(2) -Publisher FASB -URI https://asc.fasb.org//1943274/2147479806/606-10-50-13 Reference 10: http://www.xbrl.org/2003/role/disclosureRef -Name Accounting Standards Codification -Topic 606 -Publisher FASB -URI https://asc.fasb.org//606/tableOfContent + Details
Name: | us-gaap_RevenueFromContractWithCustomerTextBlock
Namespace Prefix: | us-gaap_
Data Type: | dtr-types:textBlockItemType
Balance Type: | na
Period Type: | duration