Install an evaluation instance, work through a basic surveillance task and contribute the result through GitHub.
You can contribute by testing how Sentinel installs and how its workflows behave. You do not need to write code. Start with installation and a simple disease workflow, then choose another task that fits your experience.
Each linked issue includes the steps to try and a format for reporting your outcome. Multiple people can attempt the same task. An unsuccessful attempt is useful feedback when you describe where the process stopped.
For Windows, use the evaluation-installer guide. It explains Docker Desktop, Sentinel Setup and the first-run configuration without requiring development tools. For other environments, start with the repository installation and deployment guidance.
Use synthetic data for this evaluation. Public feedback and screenshots should contain no patient information, credentials or setup tokens.
Start with tasks 1 and 2. The later tasks explore configuration, surveys and laboratory integration.
Follow the published installation instructions, start the application and create the initial administrator account. Record unclear instructions, missing prerequisites or steps that were difficult to complete.
Useful outcome: A report of the installation route, environment and outcome, including where you needed help.
Open task and report your outcome · #27 ↗Choose a disease or workflow you know. Configure a small set of custom fields and create a synthetic patient and case to check how the configuration appears in use.
Useful outcome: A description of the workflow, what worked, and a proposed change for any missing concept or unnecessary step.
Open task and report your outcome · #28 ↗Configure laboratory markers and an automated case definition. Add a synthetic result that should match and, where practical, one that should not.
Useful outcome: The expected and actual classification outcomes, with any issue in the configuration or review process.
Open task and report your outcome · #29 ↗Build a simple case-interview or contact-tracing survey. Assign it to a synthetic task or case, complete it and check how mapped values are saved or presented for review.
Useful outcome: The questionnaire and mapping purpose, the result and a suggested improvement. Note which survey builder was available.
Open task and report your outcome · #31 ↗After testing disease configuration and laboratory markers, configure a file-drop integration and process a synthetic HL7 message. Check matching, review and case-definition behaviour.
Useful outcome: The message family, expected and actual processing, and safe observations about mappings, timing or errors.
Open task and report your outcome · #30 ↗Comment on the relevant GitHub issue using its contribution-report format. Include:
For surveillance design feedback, describe how the proposed workflow would address the operational problem. Include the questions, data or decision points required.
Contact Christian with the workflow you would like to try or the skills you would like to contribute.