You must be a ticket holder to proceed
Ticket holders must sign in to LeadDev.com with exactly the same email address as stated on your ticket.
Do you have a LeadDev.com account matching the email address on your ticket?
My email is not recognised or, having signed in, it says I do not have access to the content
Double check your ticket to make sure that you are trying to access with the correct email address (see below for where to find your ticket).
If you're sure that the ticket is correct, get in touch via Slack and we'll investigate for you
The verification email does not arrive
Check your spam and/or junk folders for the email. We know that some corporate email firewalls block our emails, and in this case you'll need to get in touch (see below) for us to move your ticket to an alternative email address.
The verification email link does not work
The links are time limited, so make sure you've tried in the last few minutes. If not, some corporate email firewalls have occasionally corrupted the verification links, and in this case you'll need to get in touch (see below) for us to move your ticket to an alternative email address.
Where can I find my ticket?
Your ticket will have been emailed to you from support@tito.io (Tito is our ticketing provider). If you don't have an email from Tito with your ticket, check with the person who made the booking originally. Otherwise, get in touch and we'll be able to help.
Getting help
The quickest way to get support is via our #help-desk channel on Slack (not a member of LeadDev Slack? join here.)
You can also email hello@leaddev.com although response times will be slower.
The Community Health Toolkit (CHT) supports a vast range of open-source tools, features, and health service activities.
Through the technical stewardship provided for the CHT, Medic is committed to ensuring the tools stay updated with the newest technologies, techniques, innovations, and industry improvements to serve the community better.
To bring transparency and enhance visibility and clarity on the technology choices, the technological strategy, and the available features and tools, the CHT leverages a framework called Technology Radar.
A Technology Radar provides an easy-to-grasp visual representation of tools, languages, frameworks, platforms, and techniques, as well as features and functionalities available for use to build the CHT. Additionally, the Technology Radar provides a degree of adoption and guidelines on using (or not using) a particular technology with the CHT.
Human-Centered Design (HCD) is important at Medic and building out technology radars is no exception. In this case that shows in the form of two radars, each designed specifically for the needs of the technologists using it. Those are a CHT Technology Radar for Implementers and a CHT Technology Radar for Contributors. Both versions leverage existing open-source tools by ThoughtWorks and AOE to implement the user interface; the difference is in the content and anticipated collaborators. Due to Medic’s commitment to open-source, all the content of the Technology Radars is public on GitHub and open to the community to provide comments and suggestions.
The talk centres around the benefits of building such a tool, such as transparency, alignment and faster onboarding.
