Table 2.

System designing principles along with guidelines.

Functionality	Principle	Guidelines	Outcomes
Services	1. Service-oriented system	The designed system should be compiled with the requirements of seafarers’ health	SHES should be ready to display all the symptoms associated with the primary diseases
	2. User benefits	Seafarers could easily access the system	The system should be compatible with user requirements
	3. Integration	The system could easily integrate with user requirements	All web or desktop applications will compile with a secure application programmable interface (API). In general, API documentation provides usage and implementation characteristics
Database	4. Collection	All the data that register in the CIRM database were adequately collected and analyzed	The data analysis needs to be done in system implementation
	5. Integration	Data integration is the crucial step to transfer the data into meaningful or understandable information	Data integration improves decision making, improve customer expertise and streamline the operations
	6. Access	Easy access in data enables seafarers to make better decisions	It will help make better and quick decisions in SHES
	7. Security	All the medical records stored in SHES protected by European GDPR	SHES could manage security risk, and provide excellent data governance
Application	8. Usability	The system should be used to every seafarer despite educational background and computational knowledge	The SHES must implement an interface that allows usability function
	9. Flexibility	The SHES must be flexible to store any health records	The SHES could be a ready update to itself if any changes are required in future

CIRM: Center of International Radio Medicine; GDPR: general data protection regulation