Chat.fhir.org community expectations

Welcome to the FHIR Community chat @ http://chat.fhir.org

We welcome everyone to participate in the FHIR community. All participation in the FHIR community is subject to the Community Participation Rules: FHIR Code of Conduct and the FHIR Intellectual Property Rules. Also note: FHIR Rules for asking questions.

In addition, the following guidelines apply:

Using Streams

To subscribe to a screen, use the hidden 'gear' icon next the 'Streams' header on the left of the screen.

If you think we need a new stream, please propose it on the social stream for discussion (we don't want a proliferation of streams that aren't well differentiated)

Announcements

All users should be subscribed to the 'Announcements' stream, which is where announcements of general interest to the community are made. This stream is intended to have a "low" posting rate. Do not use it for discussions or for posts unlikely to be of interest to the entire FHIR community.

Implementers

This is the main discussion stream for FHIR Implementers. Before you post, please make sure, your question isn't a better fit to any of the Special Interest Streams.

The Implementer's Stream has a high volume of threads and responses. If you post a question, make sure to stay tuned, because if you happen to cause a vivid discussion, it may be hard to follow up, if you miss a couple of days. Please note, that FHIR has a worldwide community and discussions take place 24/7.

Special Interest Streams

• conformance: to discuss profiling, using Forge, defining extensions, publishing comformance resources, using Simplifier.net etc
• smart: to discuss the SMART framework, OAuth,
• terminology: to discuss terminology services, ValueSets, CodeSystems, using SNOMED CT/LOINC/ICD etc. with FHIR
• v2 to fhir: to discuss the challenges, when mapping HL7 V2 to FHIR or vice versa

...and many more: Please check https://chat.fhir.org/#subscriptions for a full list of available streams

Country/region based streams

There are a number of country/region based streams. These are open for anyone to follow, but if you are not from the region identified, please do not participate unless you are asked to (or ask politely first)

Members Only Streams

There are a few member only streams for governance groups (clearly marked in the stream name) - these are open so that anyone can observe, but only members are allowed to contribute (the members know who they are)

Targeting Users

It is appropriate to use @[username] to draw the attention of interested individuals to a thread, though do take care to only do so when you have reason to believe that individual would have an interest in or something to offer the discussion.

Please avoid the use of @all and @everyone on streams with large numbers of users like Implementers and Social. Topics of general interest can be posted to the Social stream or, if appropriate, to the Announcements stream. Using @all or @everyone spams everyone's inboxes and should generally only be used by chat administrators who need to proactively notify all registered users.

Search

Zulip by default only displays the most current discussions. However, there is a vast searchable history of topics. Before you post, pleast check if your question has already been aswered by using the powerful Zulip search.

Operator	Effect
stream:stream	Narrow to messages on stream stream
topic:topic	Narrow to messages with topic topic
sender:me	Narrow to messages sent by you.
is:mentioned	Narrow to messages that mention you.
keyword	Search for keyword in the topic or message content

You can use any combination of these search operators in a single query. For example:

 stream:streamname sender:user@example.com keyword

would search for messages sent by user@example.com to stream streamname containing the keyword keyword.

Rules for Asking

Please refer to the rules for asking questions

GDPR Statement

• Contributions to this forum are considered public domain under the terms of the FHIR Code of Conduct and the FHIR Intellectual Property Rules.
• Any individual or organization is able to read any public streams, and perform analytics etc on them
• HL7 is required to retain records of contributions to the standards process, and so the FHIR Foundation cannot erase contributions to this public forum (no GDPR erasure). There is no technical facility to remove contributions to private streams
• The FHIR Foundation will never share any non-public information about chat.fhir.org with any 3rd party organization
• The FHIR foundation may perform traffic analysis on all the public streams and share the results with HL7. The analysis outcomes will not be shared with any other organizations, unless they are posted publicly on chat.fhir.org etc.