get involved
How can I get involved?
Ever is built by people from many backgrounds: engineers, doctors, nurses, pharmacists, coders, translators, researchers and patients. Whatever you do, there is a way to help.
before you start
One rule for everyone
Never share real patient data. Contributors work only with test data, screenshots with names removed, and research data that is consented and de-identified.
What we hold in common
Patients first, standards over lock-in, auditable by default, and local knowledge leads.
community →There is no forum or chat yet. The community runs by email at [email protected] for now, and we answer every message.
Developers
Standard interfaces mean a small team can connect a laboratory, a device or a whole hospital system.
- read
Learn how it fits together
Architecture, interfaces, self-hosting and the plug-in model.
For developers → - source
Get the code
The public release is being staged. Until then, apply for medOS Lite, the open-source edition.
Request source access → - build
Connect a system
Connect a laboratory analyser, an imaging system, a pharmacy robot or another hospital system over FHIR R4 or HL7v2.
- build
Write a plug-in
Solve a need in your hospital or country, and share it so the next hospital does not have to.
- docs
Improve the documentation
If a guide confused you, it will confuse the next person too.
- report
Report a bug or security problem
For security issues, please tell us before telling anyone else.
Report by email ↗
Doctors, nurses and pharmacists
Most of what makes hospital software good is knowing how care is actually given. You do not need to write a line of code.
- no code
Walk through a workflow
Admission, a ward round, dispensing or discharge: tell us where it slows you down.
- no code
Review your specialty
Forms, order sets and clinical rules. Flag a field that is missing, misleading or in the wrong order.
- no code
Check the lists
Drug, laboratory and diagnosis lists against what your hospital really uses.
- data
Label data for clinical AI
Expert labelling in your specialty through AnnoMed.
AI Solutions → - email
Offer to review
Tell us your specialty and country, and we will send you something to look at.
Offer to review ↗
Researchers and academics
Medical informatics, epidemiology, public health, health economics or machine learning: there is open work across the system.
- study
Patient-held records
How people see, carry and share their own health data, and what data sovereignty means in practice.
- data
Population health
Consented, de-identified data for surveillance and outcomes research.
Clinical Research → - ai
Clinical models
Build and test models on multi-omics and health-record data.
AI Solutions → - study
Evaluate it in a real setting
Usability studies, safety reviews and before-and-after studies of a ward or clinic.
- email
Propose a collaboration
Tell us your question, your institution and what data you would need.
Propose a collaboration ↗
Hospitals, clinics and ministries
What one hospital needs today, the next hospital will need tomorrow. Health systems shape Ever by using it.
- pilot
Pilot one department
Start small before deciding on more.
How a pilot is scoped → - grant
Apply for a grant
Up to USD 30,000 a year for public, non-profit and rural facilities, and facilities in low- and middle-income countries.
Ever grants → - free
Run it yourself
Run medOS Lite, the open-source edition, on your own servers. Public health care in eligible countries pays no licence fee.
Source access → - network
Join the exchange
Let patient records move safely between your facilities and others.
- share
Share what you use
Requirements, forms and reports help the next hospital in your country.
Send them to us ↗
Make a country correct
Every country needs its own language, payer schemes and rates, codes, forms and mandatory reports. People who work in that health system know where it is wrong.
- translate
Translate clinical labels
Medical words need a medical reader in your language.
- review
Check payer rules
Compare insurance and claim rules with the latest official notices.
- share
Supply templates
Ward, department and form templates used in your country.
- email
Tell us your country
We will match you with the country pack that needs you.
Tell us your country and language ↗
Non-technical skills
If you are not a developer or a clinician, it can be hard to know where to start. Here are some ideas.
- write
Write and explain
Explain patient data ownership and interoperability in plain language, or write a step-by-step guide for staff in your role.
- write
Tell a story
Share what changed at your hospital for the Newsroom.
Newsroom → - test
Test a release
Follow a short script with test patients before a release reaches a hospital, and write down what goes wrong.
Volunteer as a tester ↗ - meet
Run a meetup or workshop
Bring clinicians, IT staff and students together to look at one workflow. We can join remotely and send material.
Tell us where and when ↗ - notes
Take notes on calls
Review sessions move faster when someone writes down what was decided.
Offer to take notes ↗
Patients and carers
Patients should help decide how people see, carry and share their own health record.
- review
Review the patient app
Tell us what is confusing or missing in the patient app and portal.
- voice
Join the patient voice group
Patient advocates and support groups are welcome.
Join the group ↗
Finance and billing staff
Hospital billing is where software most often fails. People who close the books know where the numbers do not match.
- review
Follow the money
Review how charges, claims and payments flow from the ward to the cashier and the payer.
- review
Check claim rules
Compare claim and insurance rules for your country with what payers actually accept.
- review
Check the reports
Accountants: check that reports and exports fit how hospitals close their books.
Product, design and marketing
A clinician on a night shift should never have to hunt for a button.
- design
Make busy screens calmer
Help redesign the screens staff use most, so they are faster and safer.
- product
Turn wish lists into plans
Help a hospital turn a long wish list into a short, ordered plan.
- comms
Explain why it matters
Help hospitals, ministries and patients understand what Ever is and why patient data ownership matters.
Students
Students in medicine, nursing, pharmacy, public health and computing are welcome.
- learn
Learn on a real system
Test releases, review forms in your field, translate or label data.
- build
Build a course project
Build something small on the system for your course, or ask your teacher about using it in class.
- email
Write to us
Tell us your faculty and year.
Write to us ↗
Jobs at Ever
Want to work on this full time? Ever hires engineers, clinicians, implementation staff and project managers.
- jobs
Open roles
See what we are hiring for now.
Careers → - email
Send your CV
If you do not see a role that fits, tell us what you are good at.
Send your CV ↗
Questions people ask
Do I need to be a programmer?
No. Clinicians, translators, finance staff, students and patients all have a part. Most of what makes hospital software good is knowledge of how care is given.
Do I need permission from my hospital?
To review a workflow with test data, no. To share your hospital's own forms, reports or requirements, check with your hospital first.
Is contributing paid?
Community work is voluntary. Hospitals and programmes can apply for an Ever grant, and the jobs section lists paid roles.
Not sure where you fit?
Write to us and tell us what you are good at. We will suggest a place to start.
Join the transformation today.
Ever was created from the ground up in partnership with pioneering engineers and expert physicians. Our innovations solve real-life issues that inhibit medical institutions around the world.
