Contract design thinking: a service oriented architecture SOA for contract models, maintenance and testing

Description

Contract variances complicate academic medical center accounts receivables because they are one driver of ambiguity when calculating future free cash flows FFCF [1]. UC Health provides leadership and strategic direction for UC's five academic medical centers and 18 health professional schools. Contract variations within 1 (one) medical center has a multiplier effect in the consolidated annual financial reporting. In December 2017 we created an internal project charter [2] to consolidate contracts financial accounts receivables activity (including system optimisation) within a revenue cycle operations department. Importantly, this project charter integrated managed care contracts built is a second Epic application (Tapestry). Prior to this, information technology IT staff made systems changes (in the Resolute application only). This work was driven by direct communications from the contract negotiation functions at UCSD Health. In April 2018, we started a collaboration with the University of California San Francisco Medical Center. At the highest level, the collaboration was intended to address a fragmented finance and contracts management landscape built up over time. These…

Description from Zenodo, shortened.

Files (3)

• TXTdsd059 attribute proprietary e024918 epic data structure definition contract.txt6.3 kB
• —qpBlKmWAueE8I-220 kB
• TXTd078 2018 14 093 3 1 8 21 post 0000 0001 5537 0824 c felker.txt6.8 kB

DataHunter does not store or host these files: every link leads to the original source. Check the license there before using the data.