1 / 36

Objectives

Objectives. Applying the MITA business processes Maturity level 3 Using Standards (HL7, UML) for information modeling Model-driven architecture manage the model and generate both documents and implementation artifacts from the single model Developing implementable specifications WSDL XSD

cyma
Download Presentation

Objectives

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Objectives • Applying the MITA business processes • Maturity level 3 • Using Standards (HL7, UML) for information modeling • Model-driven architecture • manage the model and generate both documents and implementation artifacts from the single model • Developing implementable specifications • WSDL • XSD • Common information and terminology • HL7 Version 3 (www.hl7.org) • Reference Information Model

  2. Narrative business process PM Enroll Provider Tier 3: Enroll Provider Item Details Links Description Trigger Event Result Business Process Steps Shared Data Predecessor Successor Constraints Failures Performance Measures Word/PDF document Evolution of MITA from doc …

  3. Narrative business process PM Enroll Provider Tier 3: Enroll Provider Item Details Links Description Trigger Event Result Business Process Steps Shared Data Predecessor Successor Constraints Failures Performance Measures Word/PDF document … to a complete model

  4. Toolboxcustomized ProviderManagement ProviderEnrollment Business Process Model browser Tools Glossary … using UML tools

  5. How to… • Use the narrative to populate UML business process • Business Process • Details • Dependencies • Import HL7 Version 3.0 information models • shared data/information detail • terminology • Use UML to document the system interfaces • Common interfaces for interoperabilty

  6. MITA Business Process Enroll Provider

  7. Trigger, Result, Steps

  8. Shared Data, Predecessor, Successor

  9. Business Steps

  10. Constraints, Failures, Performance Measures

  11. Tier 3 Business Process Hierarchy

  12. Dependencies

  13. Narrative PM Enroll Provider Process Input Data Tier 3: Enroll Provider Item Details Links Description Trigger Event Result Result Trigger Business Process Steps Shared Data Predecessor Sub-process (dependency) Successor Constraints Failures Performance Measures Business Process (High-level) Evolution … Refinement

  14. Input Data Result Trigger

  15. Benefits… revisited • Common specification • Maximize the reuse of business process and services (Enterprise Business Capability in the context of Service Oriented Architecture) • Interoperability between components developed by different projects or vendors • “plug-and-play” interoperability • TAC Enroll Provider demonstration

  16. Using MITA for interoperability • To fulfill the business process several systems must interact • Invoke behavior • Request/response • Query/response • Exchange information • Using a common specification • Semantic interoperability • Common terminology • Common structure • The following slides are views of a single UML model • Class diagrams (information, interactions, structure) • Sequence diagrams (behavior, service use scenarios)

  17. Enroll Provider System Enroll Provider Provider Registry Manage Provider InfoInquire Provider Info Enroll Provider Demo

  18. Integration Use Cases

  19. Invalid request New providerapplication Validrequest Approved request State Transition Diagram: provider’s application

  20. Business process

  21. Business process - structure

  22. Basic flow

  23. Sample Scenario

  24. Demo scenario

  25. Shared information

  26. HL7 Standard Message Structure • Imported from HL7 approved standards

  27. Detailed information model: Healthcare Provider (role)

  28. Detailed information model: Healthcare Provider (role) • We reuse reference HL7 class names, attributes, data types, code sets • We reuse internal HL7 code sets, where appropriate • We reuse standard coding systems (ICD, SNOMED, X12, NCPDP, etc.) as necessary • In the future, additional Medicaid codes may be submitted to Standard Development Organizations for a adoption through a consensus process • Benefit: Industry-standard code sets can be used in place of state-specific codes to enable semantic interoperability • The HL7 Reference Information Model is extensive and includes a variety of contributions (industry, government, international) and it meets the needs of the Medicaid

  29. Re-usable Allows us to avoid platform compatibility issues HL7 Data types

  30. HL7 Terminology Code Sets Validation of messages

  31. Enroll Provider Service

  32. Provider Registry

  33. Web Service Description

  34. Model-driven approach • As requirements change, we change the UML model • re-generate user documentation • re-generated WSDL • Diagrams provide views on the model • an element change is automatically reflected in all the diagram that use the element

More Related