1. Domain Driven Design and RIM

2. Introduction 1 RIMResistance is Futile, you Will be Assimilated!

3. Agenda RIMBAA Experiences Domain Driven Design Applied FIHR with DDD 2

4. Agenda RIMBAA Experiences Domain Driven Design Applied FIHR with DDD 3

5. Experiences from the field 4 RIMBAA Challenges – Object Oriented skills not mainstream – Developers dependencies on frameworks – ORM not needed – What !!! – RIM knowledge required – Data Types – I agree! – HL7 2.x perception

6. Current RIMBAA Project 5 Fresenius Health Care NA – 2000 Kidney Dialysis Clinics – 200k Active Patients – RIMBAA HIE Platform – Central Patient Administration – Coexist with legacy applications – Project needs to evolve in Agile environment

7. Agenda RIMBAA Experiences Domain Driven Design Applied FIHR with DDD 6

8. Architecture 7 Domain Driven Design & RIM – Vital Patterns Bounded Context (Universal Domains) Aggregate Root (R-MIM) Specification (Constraints, Business Rules) Event Sourcing (State Storage, Ultimate Audit) Command Query Responsibility Segregation (RIM Isolation)

9. Bounded Context 8 User Interface View Model RIM RIM Events Segregation Commands Query Events Any

10. Patient Administration 9 Patient Tracking Current State R-MIM AmbulatoryEncounter Event Segregation Commands Query Changed Data 2NF

11. Agenda RIMBAA Experiences Domain Driven Design Applied FIHR with DDD 10

12. Challenges 11 Restful RIM Resources – CRUD theme – Whats a Resource – Future Proof – Local Extensions – Other Protocols – Deployment schemes

13. Patient Administration 12 REST Resource R-MIM AmbulatoryEncounter Event Segregation Post Get Changed Data CCD

14. Patient Administration 13 REST Resource R-MIM AmbulatoryEncounter Event Post Get Changed Data Resource Message

15. 14 Patient De-Identify Deployment Example Command BIDMCBWHCHBMGHMIT Segregation Resource or Views Firewall R-MIM