If you need an introduction for this GitHub ‘GIDS Open Standaarden’ or more background information in Dutch, click here.
Issues with components? Please report issues in the relevant repository and use "@name"to assign a member. If you want guidance, please follow the good practice shared by testlio here. Alternatively, you can always contact us at info@gidsopenstandaarden.org.
We distinguish between five states for open source components:
- R&D: we are still researching, describing, and conceptualizing.
- POC: Proof of Concept, a first implementation is being realized and tried out. Cannot be used in beta or production settings.
- Beta: the component is used in a few places.
- Production: the component is used in many places.
- Abandoned: we do not, or no longer maintain and/or support the component. Contact the developer directly if you want to obtain support, or contact us if you want to contribute and re-activate an open source component.
HTI is an open standard that support the shared function 'to start third party applications' anonymously. It is inspired by the proven international education open standard IMS-LTI and can be (re)used in different initiatives, like Beter met Elkaar, MedMij, and Koppeltaal. It succeeds and replaces SNS/Launch, see below.
- GIDS-HTI-Protocol technical specification.
- GIDS-HTI-TestSuite intended for developers to support the implementation of the HTI protocol.
- GIDS-HTI-RI-Module-Python code example.
- GIDS-HTI-RI-Module-Java code example.
- GIDS-HTI-RI-Portal-Java code example.
Currently, we develop SNS in 3 phases of open source components to start third party applications (eHealth modules) from portals (1. SNS/Launch), and to identify users arriving in a module from a portal through such a launch using IRMA (2. SNS/Identity). We are working on components to connect social networks to healthcare contexts, such as community portals or personal health record applications (3. SNS/Community).
We strongly advise current users to implement GIDS Health Tools Interoperability (HTI), see above. HTI succeeds and replaces the SNS/Launch protocol. SNS/Launch is in use in Stichting Beter met Elkaar projects; SamenBeter Proeftuin Wijken and FitKnip Duurzame Financiering.
- OpenSNS-Launch-Protocol technical specification.
- OpenSNS-Launch-Emulator test tool for consumer and producer.
- OpenSNS-Launch-Java code example.
- OpenSNS-Launch-PHP code example.
- OpenSNS-Launch-Python code example.
To authenticate and authorize we use IRMA, for example when users arrive in a third party application via HTI or when accessing their Solid Pod.
- OpenSNS-IRMA-Auth tool to abstract implementation complexity away from other applications.
- OpenSNS-IRMA-Docker contains the containerized deployment of an IRMA go server.
To prove that a portal and module application can store data using FHIR in a personal data store. Reference implementation of a portal has been made. To list e-health tasks and use HTI to anonymously launch these tasks, to connect to a Solid POD and give read / write access.
- OpenSNS-Community-RI-Portal-Java code example.
- OpenSNS-SolidClient-Java tool to provide applications access to Solid Pod.
Frameworks that help you implement policies more easily for governance, risk and compliance. As you make use of, or contribute to our GIDS Open Standaarden open source components.
- GIDSOpenStandaarden-SecurityFramework. [Beta] instructions for peer review or external audit.
- GIDSOpenStandaarden-PrivacyFramework. [Beta] principles for privacy by design.
- GIDSOpenStandaarden-LegalDocuments. [Beta] legal commons, licences, processing agreement.
- GIDSOpenStandaarden-Templates. [Production] template naming repositories.
We share open source components to help implement the functions required to participate in MedMij, a set of agreements to enable Dutch personal health record (PGO) applications (OpenPGO). Please take note that currently these components are not updated to the most recent version of MedMij.
The decision has been made to archive the repositories. The reason is that the building components are not being used and have deferred maintenance including security vulnerabilities. If you want to use the components, please check them for compliance first, and if needed, update them to the latest MedMij version.
Contact the developer directly if you want to obtain support, or contact us if you want to contribute. We are working to organize financial support to further develop and maintain these components.
- OpenPGO-Medmij-ImplementatieBouwstenen-Opdracht. Assignment for the participants in the challenge to make the MedMij implementation building blocks
- OpenPGO-Medmij-ImplementatieBouwstenen-Java. Java implementation of the MedMij implementation building blocks.
- OpenPGO-Medmij-ImplementatieBouwstenen-Dotnet .NET implementation of the MedMij implementation building blocks.
- OpenPGO-Medmij-ImplementatieBouwstenen-NodeJS Node.js implementation of the MedMij implementation building blocks.
- OpenPGO-Medmij-ImplementatieBouwstenen-PHP. PHP implementation of the MedMij implementation building blocks.
- OpenPGO-Medmij-ImplementatieBouwstenen-Python. Python implementation of the MedMij implementation building blocks.
- OpenPGO-Medmij-ImplementatieBouwstenen-Python-OAuth Python implementation of the MedMij OAuth Flow.