Capitalized hospital information systems and EMR software

HIS/EMR implementations run into the millions and blend feasibility, configuration, training and support costs that are treated very differently under IAS 38; blanket capitalization inflates assets that must later be impaired when a mandatory NPHIES-type regulatory upgrade shortens useful life, while blanket expensing understates genuinely capitalizable system-build costs and distorts year-on-year cost comparability.

Has the project moved beyond the feasibility study and vendor selection stage into actual configuration, coding and integration build, with clear management intent and ability to complete and use the system? Are internal payroll costs of IT and clinical staff working directly on the build tracked separately from ongoing support and helpdesk costs? Are training and data migration/cleansing costs, which are generally expensed, clearly distinguished from system configuration costs that may be capitalized?

1) Map the project into phases: preliminary/feasibility (vendor evaluation, requirements gathering), application development (configuration, coding, integration build, testing), and post-implementation (training, data conversion, ongoing support). 2) Expense preliminary-stage costs and post-implementation training/data-conversion costs as incurred, regardless of overall project size. 3) Capitalize direct costs of the application development stage (configuration, customization, integration, testing) only once there is a clear intent and ability to complete and use the system. 4) Track internal payroll costs of staff directly engaged in configuration/build separately from ongoing IT support costs, capitalizing only the former during the development stage. 5) Amortize the capitalized intangible over its expected useful life once the system is ready for its intended use, considering technology obsolescence and mandatory regulatory upgrade cycles. 6) Reassess useful life (and test for impairment if indicated) whenever a mandatory platform change materially shortens the system's remaining useful economic life.

Measure at directly attributable cost including internal payroll time of staff directly engaged in configuration/build, and third-party implementation fees, excluding general overhead and support costs not directly attributable; amortize over the expected useful life considering technology obsolescence and mandatory regulatory upgrade cycles (e.g. periodic claims-platform specification changes), not a default long period; test for impairment whenever a regulatory or technology change signals the system's remaining useful life is shorter than originally estimated.

Disclose the carrying amount, amortization method and useful life of significant capitalized systems (HIS, EMR, claims integration platforms); disclose the amount of IT costs expensed as incurred versus capitalized during the period; disclose any changes in useful life estimates driven by mandatory regulatory platform upgrades and the resulting effect; disclose impairment charges, if any, following a major system replacement decision.

• Capitalizing the entire IT project budget including training, data cleansing and post-go-live support instead of only qualifying configuration/build costs
• expensing genuinely qualifying configuration/development costs due to a blanket policy of expensing all software spend
• not reassessing useful life when a mandatory regulatory platform change (e.g. a claims-integration version upgrade) shortens the asset'
• s remaining useful economic life
• capitalizing internal payroll costs of staff not directly engaged in the build (e.g. general IT helpdesk)
• failing to separately track internal labor time, making capitalization decisions unsupportable on audit.