See my post over on the official FHIR Product Director blog.
The FHIR team is continuing to grow, and has plenty of opportunities for more people to contribute. Here are some of those opportunities:
Core FHIR spec
We’re looking for:
- people from committees to work within committees to improve the definitions for resource, data type and profile elements and codes
- implementers to work with the editors to develop further realistic high-quality examples that fill out resource usage
- anyone who wants to work on proof-reading,
- more committee members to learn how to edit specifications to give us more depth in the committees
We’re looking for:
- a fhir.org web developer. If you know drupal, and you’re a member of the fhir+hl7 community, you can help with the various fhir.org services
- more people to respond to questions on community.fhir.org
HAPI and the C# reference implementations would love to get more active contributors.
There are several roles:
- first responder – answer questions about using them in various social media
- tester – maintaining and extending the automated tests, and manually testing what can’t be automatically tested
- documentation – contributing how-to and core documentation, and explaining how the RIs compare to the spec
- committer – code contributors are also welcome
You can contribute to these as much as you like – a few hours here and there, up to full time.
If you’re interested in contributing in any of these roles, let me know (at firstname.lastname@example.org), and I’ll connect you up with the right team member. We will be happy to provide support and direct you to necessary training material and documentation and/or set up mentor/mentee relationships to help you through the process. If you’d like some justification to share with your manager/employer, we may be able to help there too.
If you have other ideas about how you’d like to assist, those would be welcome as well.