Perspectives

Encompass's single-user-per-file limitation creates processing bottlenecks that scale badly with volume. The UI, broadly described in review platforms as a Windows 95 experience, generates consistent friction for loan officers and underwriters. Administrative configuration is deep, brittle, and expensive: lenders routinely carry high admin-to-loan-officer ratios just to maintain Encompass stability.

The Implementation Boundary is the structural gap between the EHR vendor's contract scope and the health system's custom-built data infrastructure: the HL7 integrations, CCL reports, data pipelines, and FHIR applications that neither the vendor nor the implementation consultant owns. It does not appear on the project plan.

Every acquisition hides technology risk, including legacy code, brittle integrations, undocumented workflows, fragile data pipelines, and engineering practices held together by tribal knowledge. None of this appears in IMs or management decks, and none of it is quantified in the valuation.