Difference between revisions of "FHIR Rules for asking questions"
Line 22: | Line 22: | ||
# when possible, provide references into the specification or other authoritative specification to back up what you're saying | # when possible, provide references into the specification or other authoritative specification to back up what you're saying | ||
# if someone asking a question has identified an area where the specification is unclear or could be improved, encourage them to submit a change request - this helps broaden the pool of those who are working to improve the specification and also increases a sense of ownership | # if someone asking a question has identified an area where the specification is unclear or could be improved, encourage them to submit a change request - this helps broaden the pool of those who are working to improve the specification and also increases a sense of ownership | ||
+ | |||
+ | See also [[http://stackoverflow.com/help/how-to-ask Stack Overflow Question Guidelines]] | ||
+ | |||
+ | == Why are you here? == | ||
Mostly, you'll end up at this page if someone referred you here. That means that they think your question (or maybe your response) didn't meet these guidelines. That doesn't mean you can't ask the question or respond, but it does mean you might want to try harder to not take the service for granted. | Mostly, you'll end up at this page if someone referred you here. That means that they think your question (or maybe your response) didn't meet these guidelines. That doesn't mean you can't ask the question or respond, but it does mean you might want to try harder to not take the service for granted. | ||
− | |||
− |
Revision as of 05:01, 8 December 2016
Many members of the FHIR community generously give their time for free, answering other implementer's questions on various social media forums.
Some of the forums in which FHIR Community Members are regularly available:
Please note, however, that this is all provided by volunteers.
If you're going to ask a question, please take note of the following guidelines:
- be specific - provide enough information for someone who might answer the question to actually do so
- be clear - what are you asking for?
- Don't ask questions that can be characterised as 'please do my homework for me' - you'll get better answers when when your question is very focused
- Show in asking the question that you've done a bit of work yourself - indicate what you've read or where you've already looked (at minimum, reading or searching the specification and searching chat.fhir.org is encouraged)
By the same token, responding to others who ask questions is encouraged. You don't need to be an "expert" or a member of any particular work group. Answering questions is a good way to build credibility within the community and to give back. That said, there are some guidelines here too:
- try to only answer questions when you're relatively confident that you know the answer to
- try to distinguish when you're asserting fact vs. opinion
- if you're not completely confident in the answer, don't be afraid to indicate that
- when possible, provide references into the specification or other authoritative specification to back up what you're saying
- if someone asking a question has identified an area where the specification is unclear or could be improved, encourage them to submit a change request - this helps broaden the pool of those who are working to improve the specification and also increases a sense of ownership
See also [Stack Overflow Question Guidelines]
Why are you here?
Mostly, you'll end up at this page if someone referred you here. That means that they think your question (or maybe your response) didn't meet these guidelines. That doesn't mean you can't ask the question or respond, but it does mean you might want to try harder to not take the service for granted.