Table 2 Requirements for a consent template exchange format
From: MAGIC: once upon a time in consent management—a FHIR® tale
Requirement | Description |
|---|---|
Portability/extensibility | Essential gICS-information have to be transformable into the selected standard/format, or the selected standard/format offers necessary degrees of extensibility |
No license fees | gICS is published under open source license (AGPLv3) and, thus, is free of cost for users. As a consequence, implementation and use of the proposed exchange format must not raise additional costs in terms of license fees for developers as well as users |
Comprehensive developer support | To minimise implementation efforts, the selected standard/format has to offer a comprehensive support for developers and related development procedures including contemporary (web-based) technologies, support for parsing, validating, encoding and decoding the proposed format. Moreover, the use of maven repositories and an active developer community (e.g. blogs, chats or direct contact partners) for further inquiries or bug reports are preferable |
Dissemination | The selected format/standard has to be already implemented in the scientific community (i.e. not being in conceptual, draft or prototypic state) in order to allow an implementation during the runtime of the MAGIC project |