Skip to main content
. 2019 Oct 7;21(10):e13585. doi: 10.2196/13585

Table 2.

Consolidated requirements of stakeholder groups for a blockchain-based electronic health record.

No and group Requirement References E1 E2 E3 E4 E5 E6 E7 E8 E9
Primary stakeholders
R1 Data securitya [7,12,20] b x x x x x x x
R2 Data privacya [7,12,20] x x x x x x x x
R3 Access/permission control, data sovereignty [8,20-22] x x x x x
R4 Identity confirmationa [8,20] x x x x x
R5 Manipulation protection/data integritya [7,21,23,24] x x x x x x
R6 Complete health recorda [21] x x x x x x x x
R7 Performancea [7] x x x x
R8 User friendly designa [25] x x x x x x x
R9 Context-specific informationa [25] x x x x x x
R10 Data and file storinga [20] x x x x x x x x
R11 Data and file sharinga [8,12,20,21] x x x x x x x x x
R12 Interoperable and consistent data standardsa [12,20] x x x x x x x
R13 Intersectoral communicationa [12,21] x x x x x x x
R14 Ensuring trusted relationshipsa [12,20] x x
R15 CRUDc rights [8,21] x x x x x x
R16 Verification modus [8,21] x x x x
R17 Emergency pass [26] x x x x
R18 Medication/care plan [27,28] x x x x x
R19 Tracking of state transitionsa [8] x x x x x x x
R20 General administrative issues x x x
R21 Synchronization to off-chain dataa [8]
R22 Notification services [8] x x x x x x
R23 Modularitya [20] x x
R24 Patient centration [12] x x x
R25 Workflow supporta [29] x x x x x
R26 Integration into existing systemsa [8,29] x x x x x x x
R27 Transfer sheet x x x x x x
Secondary stakeholders










R28 Scalabilitya [7,12,20] x x x
R29 Invoice management x x x x
R30 Modus for relatives x x x —x
Tertiary stakeholders










R31 Access to consolidated dataa [10] x x x
R32 Statistics [10,30] x x x
R33 Clinical research [31] x x x x
R34 Predictive analyses [31] x x x x

aTo avoid multiple entries, requirements that apply to all stakeholder groups, for example, data security and data privacy, are listed once.

bNot applicable.

cCRUD: create, read, update, and delete.