Soarian Financials (SF) Principal Consultant

** Job Description*
* The role will facilitate and coordinate activity between the Oracle teams supporting Office of Mental Health (OMH), inclusive of Application Management Support (AMS), Upgrade Center, Help Desk and Contract Management and Recovery Services (CMARS).

** Responsibilities*
* *
* Responsibilities include:

*
* ** Business Operations:*
* · Monitoring daily claims production

· Monitoring and resolution of any claim transmission errors to the clearinghouse

· Adjusting Claims Rule Development Tool (CRDT) rules to meet payer requirements

· Monitoring of system generated charges and resolution of charge posting failures.

· Management of all third-party licenses and maintenance agreements for hardware and software used in the operation of the Billing System.

** Technical Operations:*
* · Monitoring and reconciliation of all system interfaces (i.e., OMH EMR, remittances, OMH data warehouse, etc.), including the identification and resolution of transmission failures.

· Monitoring and resolution of any claim transmission errors to the clearinghouse. Actively monitoring and ensuring successful completion of all system scheduled and unscheduled activities, processes, and functions.

· Monitoring system performance to ensure all the required service level agreements (SLAs) are met.

· Job monitoring (ex. Validate that all scheduled jobs are successful and remediating any issues or failures that occur).

· Work in conjunction with help desk support, Upgrade Center, and Application Management Support (AMS) to manage database administration and change control functions.

· Ongoing Services include Solution Architect which includes working in conjunction with Cerner Client Alignment Executive, Upgrade Center Team, AMS and when applicable, the contract management and recovery services (CMARS) team to provide ongoing services to support and maintain the Billing System. These services include:

· A roadmap of planned releases and upgrades

· Maintenance and upgrades to Billing System

· Notification of all system changes including Release Notes

· Testing of all releases, including planning for and facilitating UAT testing for pre- and post-Go Live releases

· Management and deployment of updated versions of firmware and software for all environments. Fulfillment of approved service requests for changes to the Billing System which include updates to system functionality configurations, or localizations including system tables (i.e., charge master, provider master, etc.), dropdowns, data fields, billing edits, billing rules, etc.

· Maintenance:
Initiated by the Vendor, or the upgrades, patches, hardware, and software changes etc. that are necessary to maintain and improve the Billing System over time and keep the Billing System compliant with all requirements. The Solution Architect will work in conjunction with the Cerner Client Alignment Executive, Upgrade Center Staff and AMS and CMARS representation when applicable to organize and complete the following events

· Maintenance changes must be categorized, reviewed, approved and time frames communicated to OMH through the Change Management Process. Changes may include system patches, security upgrades, changes to Federal and New York State regulations, policies, and standards, as well as changes to payor practices.

· Service Requests:
These are requests for support or changes to be made to the Billing System in the following categories:

· Incident:
An unplanned disruption in system or business operations either reported by OMH users, found by the Vendor's staff, or uncovered by the Vendor's monitoring tools. Incidents are reported to the Cerner Help Desk and tracked in Cerner's ticketing system. Those incidents that are determined to be an error, flaw, mistake, failure, or fault in the Billing System are considered a defect.

· Incidents are researched by the Cerner Help Desk, triaged and the severity level is determined by the impact

· Time frames for resolution are established based on the severity level

· Incidents would not be processed through the change management process unless the incident was identified to be a defect which required a change to the system to resolve. If found…