A small source for IT students at the VFU, Varna.

1. Architecting
digital
systems
Module 5
Practical work
Alexander Samarin

2. • The IFRC (see www.ifrc.org) wants to have a standard
information system for their medical Emergency Response
Units (ERUs) – RCHIS2020
• Medical ERU type 1 - point-of-care has four core functions:
– reception
– triage
– consultation
– pharmacy
• Medical ERU type 2 - hospital has extra core functions:
– inpatient wards
– operating theatres
– delivery room
– pharmacy
– laboratory
– x-ray
© A. Samarin 2018 Architecting digital systems - Module 5 2
Outline

3. 1. To facilitate management of patients inside the health
ERU and clinical decision-making, to monitor and improve
quality of care.
2. To provide rapid analysis of clinical data allowing for
surveillance and detection of potential outbreaks.
3. To simplify reporting to headquarters, donors and
partners.
4. To facilitate the management of the health ERU in terms
of staff management and drug and consumables stock
management and supply.
© A. Samarin 2018 Architecting digital systems - Module 5 3
The main goals of the RCHIS2020

4. 1. Electronic Medical Record to support clinicians in decision
making and quality of care.
2. Health facility-based surveillance to identify potential
risks of outbreak.
3. Reporting and accountability to a range of financial and
operational partners.
4. Health facility management to improve the efficiency of
operations.
© A. Samarin 2018 Architecting digital systems - Module 5 4
The full version main functionality

5. © A. Samarin 2018 Architecting digital systems - Module 5 5
The module I – only for-outpatient
department (OPD) functionality

6. © A. Samarin 2018 Architecting digital systems - Module 5 6
The module I outline

7. © A. Samarin 2018 Architecting digital systems - Module 5 7
Patient carepath

8. © A. Samarin 2018 Architecting digital systems - Module 5 8
Access rights to patient’s data

9. © A. Samarin 2018 Architecting digital systems - Module 5 9
Architectural challenges

10. © A. Samarin 2018 Architecting digital systems - Module 5 10
High-level architecture

11. © A. Samarin 2018 Architecting digital systems - Module 5 11
Various configuration (1)

12. © A. Samarin 2018 Architecting digital systems - Module 5 12
Various configuration (2)

13. • ARC-01 Outline the main concepts of your platform-
based architecture
• ARC-02 Explain how the platform-based architecture
addresses the RCHIS 2020 architecture challenges
• ARC-03 Outline your approach to API and how will you
implement various APIs
• ARC-04 List the primary components of the platform in
the solution. Explain your choice
• ARC-05 Outline the nature (open source or not) for
each proposed component in the solution.
• ARC-06 Evaluate the efforts for maintenance in your
solution.
© A. Samarin 2018 Architecting digital systems - Module 5 13
Architecture questions:
high-level architecture

14. • DES-01 Outline how your solution achieve the
responsive design for the user interface. HTML5 is
strongly recommended
• DES-02 Outline how your solution achieve good
ergonomic of the front-end and the app
• DES-03 Explain your approach for implementation of
multilingual front-end
• DES-04 Provide necessary details how your solutions
will be functioning with and without connectivity
• DES-05 Outline the fixed configuration
• DES-06 Outline the mobile configuration
© A. Samarin 2018 Architecting digital systems - Module 5 14
Architecture questions:
various configurations (1)

15. • DES-07 Outline the nomadic configuration
• DES-08 Outline the configurations for the field data
centre and the HQ
• DES-09 Explain how the surveillance will be
implemented
• DES-10 Outline how various IoT medical device can be
added to your solution. Estimate necessary efforts
© A. Samarin 2018 Architecting digital systems - Module 5 15
Architecture questions:
various configurations (2)

16. • PRO-01 Outline your approach for implementing
processes for medical capabilities
• PRO-02 Outline your approach for implementing
processes for business capabilities
• PRO-03 Outline your approach for implementing
processes for technical capabilities
• PRO-04 How does the solution implement role-based
assignments?
• PRO-05 How does the solution implement delegation?
• PRO-06 How does the solution implement audit trails?
User’s unique identifier, with dates, data entered, reports
sent, changes made, etc. must be captured
© A. Samarin 2018 Architecting digital systems - Module 5 16
Architecture questions:
Processes

17. • INF-01 List the supported OS for various hardware
platforms
• INF-02 Outline hosting options for your solution
© A. Samarin 2018 Architecting digital systems - Module 5 17
Architecture questions:
Infrastructure

18. • OPS-01 Outline how the solution will be monitored.
• OPS-02 Estimate the resilience (recovery point
objective and recovery time objective ) of your solution in
case of hardware failure of important components
• OPS-03 How does the solution implement the ITIL-like
incident process? Provide your support contract template.
• OPS-04 How does the solution implement the ITIL-like
problem process?
• OPS-05 Outline maintenance practices for the solution’s
components. Provide your maintenance contract template.
• OPS-06 What is the warranty period for the solution?
© A. Samarin 2018 Architecting digital systems - Module 5 18
Architecture questions:
System operations

19. • INF-01 Explain how the solution guarantees data
integrity, confidentiality and availability in various data
flows.
• INF-02 Explain how the solution guarantees data
integrity, confidentiality and availability in various data
storage.
• INF-03 Explain how the solution guarantees flexibility
of data definitions, in particular, co-existing of different
versions.
• INF-04 How does the solution implement reporting at
a medical ERU?
• INF-05 How does the solution implement reporting at
the level of operation?
© A. Samarin 2018 Architecting digital systems - Module 5 19
Architecture questions:
Information architecture

20. • INF-06 How does the solution implement reporting at
other levels (country, regions, federation and partners)?
• INF-07 Outline how ate various data storages
implemented. Relational database with SQL is strongly
recommended.
• INF-08 Forms can be developed in other systems than
DHIS2, but need to be compatible for data exchange with
DHIS2 (not just through data export).
© A. Samarin 2018 Architecting digital systems - Module 5 20
Architecture questions:
Information architecture

21. • EMR-01 How does the solution implement security of
PHWBER.
• EMR-02 How does the solution implement privacy of
PHWBER.
• EMR-03 How does the solution implement
anonymization of PHWBER.
• EMR-04 How does the solution implement identification
of patients.
• EMR-05 Explain the ability of the solution to add
various techniques for authentication of patients.
© A. Samarin 2018 Architecting digital systems - Module 5 21
Architecture questions:
SDLC and software factory

22. • MET-01 Outline the SDLC to be used.
• MET-02 Outline how the proposed SDLC is linked with
projects management practices.
• MET-03 Outline how the proposed SDLC is linked with
DevOps practices.
• MET-04 Outline what tools will be used for the
implementation of the solution.
• MET-05 Provide any existing documentation about the
proposed SDLC.
• MET-06 Provide detailed (weekly-based)
implementation planning.
© A. Samarin 2018 Architecting digital systems - Module 5 22
Architecture questions:
SDLC and software factory

23. • LAN-01 Explain how the solution handles multiple
languages (English, French, Spanish, Arabic). Note that
the user interface texts must be will be translated by
professional translators.
• LAN-02 Explain how the solution implement the
possibility that user can choose his/her screen (interface)
language
© A. Samarin 2018 Architecting digital systems - Module 5 23
Architecture questions:
language capabilities

24. © A. Samarin 2018 Architecting digital systems - Module 5 24
Questions?