MDM and SOA Timo Itälä T

Transcription

1 MDM and SOA Timo Itälä T

2 Outline Need for SOA Options for SOA Need for common master data in SOA Discovering master data Managing master data Managing external master data SOA and MDM 2

3 Recap: Putting the enterprise into the ERP system Resources Suppliers Core Processes Support Processes Organization Alignment of IT and business Organization s strategy, goals and operations Business Processes Organizational charts Conceptual models, data models Application suites Software and hardware platforms Information ERP system Infrastructure 3

4 Basic ERP architecture (Davenport)

5 Process Orientation But: Have we moved from one set of silos (functions) to another set of silos (processes?)

6 Business Process Management (BPM): The Third Wave

7 Our business process 7

8 What if... We ask the customer to do some of the work 8

9 What if... We want to share things we have 9

10 What if... Some of our things are outsourced... 10

11 What if... We then acquire a competitor who does certaing things better than we do! 11

12 What if... We then make changes to our brilliant process design on 18 months... 12

13 Service Orientation: Processes and services

14 SOA and MDM, but which to choose? The promise of Service Oriented Architecture (SOA) for business processes are cost reductions and improved agility through reuse of modular business services implemented with Web Services technology. SOA Principles: Loose coupling, Encapsulations, Independence The promise of Master Data Management (MDM) are reduced integration costs and improved business productivity through use of consistent data accross different applications of the enterprise. MDM Principles: Sharing common data and definitions, avoiding duplication Is there a dilemma between this two approaches? 14

15 Processes and services Care Processes Diagnostic services Generic services Enterprise service bus Applications with interfaces

16 SOA example: The care process and services Electronic Health Record Invoices Secondary use information: statistics etc. SOA terminology Business Process: Care Process Business Services: Lab tests, radiology tests, endoscopy tests etc... Procedures, Medication, Therapies Medication orders, therapies etc are requested services A care process consists of multiple services

17 The need for a common information model Shared understanding between the business processes and business services Master Data Who: Organization, person Patient, Doctor, Hospital, Laboratory Where: Location, address Hospital, Ward, Laboratory What: Item What to do, what to order, what to invoice, what are the results Which: Classification Which diagnosis, which specialty

18 Healthcare Information Model HL7 RIM Master Data Entities Instances of Business Processes Business Services Entities and its attributes Organizations People Places, locations Service codes Classifying codes Diagnoses Job codes Hierarchies Organization Unit Product Identifiers

19 Aggregations Encounter Id (Encounter Id, Ecxamination Id) Examination Id Aggregations: ActRelationship. Pairs of keys of related acts What services were needed to produce the results of an instance of an process? Aggregations are needed for example Electronic Patient Records: Examinations related to an encounter Data Warehousing: All examinations related to an encounter Instance of a process Instance of a service For example: Encounter and related examination Keys of instances should be considered as important master data, which need to be provided by the collaborating applications

20 The applications expose the services Every application has its own master data 20

21 Unmanaged, replicated master data Master data is managed separately in each systems Same concept can have different codes, same codes can mean different concepts The field names and field values do not match Changes are not propagated in sync Obsolete codes still exist No clear responsibilities or ownership of master data No history tracking Result: Increasing Maintenance Costs, dereasing maintenance productivity A B C D Master Data 21

22 Master Data Management in SOA environment ESB, common information model Master Data service A B C D Manual distribution of Master Data Master Data server Master Data Governance Model MD-1 MD-2 MD-3 S-A S-B S-C S-D 22

23 Service oriented Master Data Management Master Data Services Create and update services for the owners of master data Using Master Data services for the users of master data The actual physical implementation of master data is encapsulated behind the services The master data services may be used within other services Applications are not using their own code tables in their own databases but master data services ESB, common information model A B C D Master Data services 23

24 Multiple organizations sharing information OID 1 Local Master Data services MD Publish/Subscribe services MD Mapping services Global Master Data services OID 1.Encounter Id OID 2.Encounter Id OID 2 OID 3.Encounter Id OID 3 OID 4 Global Repository OID 4.Encounter Id Internal Master Data External Master Data Organization Identifiers ISO OID (Object Identifier Standard) 24

25 Owner of Master Data The source of the master data is shown in the data itself OID 1 Examples of HL7 data types OID 2 Instance Identifier (II) <id root=" " extension= 1234"/> OID 3 OID 4 Global Repository Coded Value (CV) <value xsi:type="cv" code="r07.2 displayname= chest pain codesystem=" codesystemname=" ICD > Internal Master Data External Master Data 25

26 Conclusions SOA needs MDM MDM can be implemented using SOA The SOA strategy and the MDM strategy need to be developed together 26

27 Thank You! Questions? Timo Itälä timo.itala(at)tkk.fi 27