Information Models and Master Data Management in Business Process Management

Transcription

1 Information Models and Master Data Management in Business Process Management Timo Itälä SoberIT, TKK

2 Outline Example of a business process and business services Need for common master data in SOA Discovering master data Managing master data Managing external master data SOA and MDM 2

3 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? 3

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

5 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

6 The need for a common information model Shared understanding between the business processes and business services 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

7 Healthcare Information Model HL7 RIM Who Where What What Business Events Definition: In this presentation Master Data is the static data that is referenced from transactional data that represents business events Entities and their attributes Structures Vocabularies and codes Reference Data Instances of Business Processes Business Services

8 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 A B C D Master Data 8

9 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 S-A S-B S-C S-D MD-1 MD-2 MD-3 9

10 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 10

11 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

12 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) 12

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

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

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