�ݺ�ߣ

Editor's Notes

1. Quick slide Hand off to Joe
2. My interpretation of the original diagram: When claims enter MARS issues can occur. Those issues are hard to identify and monitor. The puzzle piece image represents problems need to be searched for The code image represents broken code Monitoring and alerting represents a need for monitoring and alerting Questions: What is MCM Data? --- rename to Database What is the role of the 2nd trading partner in the slide? What does the HIPAA image represent? What is 2Data? Key Points of slide: Issues occur when claims enter MARS Those issues include: Broken/buggy code, lack of monitoring and alerts, need to search for issues Claims are difficult to enter Challenges around EDI complexity Duplicate effort to send to multiple systems Customers expect enterprise functionality such as monitoring and alerting
3. My interpretation of the original diagram: 1. Explains specific features of the T-Connect HIPAA Accelerator in further detail Questions: 1. Do arrows on right point to specific points or just the list? Key Points of slide: The 6 sections being called out (in red) Installed in 1 hr vs. 6 weeks T&M – less cost, faster time to market Can manage trading partners and agreements Enterprise level solution pre-built (tested / hardened / packaged / not from scratch) – Archive, logging, alerts, validations, acknowledgements, database persistence Core dynamically recognizes 11 HIPAA EDI types, and properly processes it and stores in canonical. Still needs to be mapped to back office system (about 3 days dev each, 4 days test) Only 1 flow into back office system per type Can scale to any amount of additional trading partners with no additional customization (would be 3 to 4 weeks)
4. My interpretation of the original diagram: Claims are sent from Trading partners and disassembled and debatched on the way to MARS Claims are transformed to XML which is archived, logged, validated, etc (bulleted list) Data is displayed in Dashboard/Portal Data is sent to MCM Database Questions: What is the role of the automation tool? What is MCM Data? What role is salesfoce/CRM playing here? – just need to represent back office system. Show that data / file flows into back office system Key Points of slide: Data from multiple partners is received and processed by our system Data is used for multiple purposes (display dashboard, alerts, crm) We have packaged a core set of functionality Additional features: Dashboard, portal, etc. – Tiers Efficient development / expandability
5. My interpretation of the original diagram: 1. The “Back-Office Package” of our T-Connect HIPAA Accelerator has extended features on the back-end Questions: What is an example of a client claim system? What is the role of client databases in this diagram? What is “Core” referring to? Is this functionality an add-on to the functionality in slide 5? Key Points of slide: Claims are sent to client claim systems after going through our back office package. Tiers of implementation – Time and materials based on complexity This is a service, offered as a value-added package
6. My interpretation of the original diagram: The WPC EDI Data Package stores EDI data in database tables Questions: What is the advantage/function of these database tables? Is this functionality an add-on to the functionality in slide 5? Key Points of slide: Data is placed in tables which allows for specific functions a business might need. Back Office package has specific functions as well (bullet points) This is IP, not a service Offer is a tiered package, depending on transaction sets (single, multiple, bundled (11)) We can build custom SSRS reports, leverage BI based on WPC schema
7. My interpretation of the original diagram: 1. T-Connect Trading Partner Package has several features which gives information about the trading partner Questions: Where does claim go after entering TP Package? What “Receives messages from TP”? Arrow points to claim’s original position ? Is the TP Package communicating with the trading partner or just the claim? Is this functionality an add-on to the functionality in slide 5 and 8? Key Points of slide: Claim enters T-Connect through TP Package which has many features for the Trading Partner Will be tiered packages (single, multiple, bundle) Custom mapping from Trading Partner to canonical Uses Trading Partner Automation tool to implement this quickly Simple mapping exercise by using canonical schema, just doing EDI to EDI
8. Quick slide Hand off to Joe
9. Quick slide Hand off to Joe
10. Quick slide Hand off to Joe
11. Quick slide Hand off to Joe
12. Quick slide Hand off to Joe
13. Quick slide Hand off to Joe
14. Quick slide Hand off to Joe