...
We aim to find opportunities where ClinSpark users and Foundry Health our product team can interact in an open, transparent manner. We also want to see customers share ideas, challenges, and discuss best practices with each other.
...
Slack is a real-time communication platform that was setup to allow users to engage with ClinSpark subject matter experts. It is currently used as a release announcement channel and a way for community members to engage in chat with other ClinSpark users and Foundry Health product team members on various topics.
Access to the ClinSpark user community is managed through invitation (via Service Desk). Or, if someone within your organization is already a member of the community, they can also request a member invite directly in Slack.
Some of the Foundry Health product team are present in the Slack community to oversee platform administration and facilitate discussions.
...
Groups.io is a platform managed entirely by members of the ClinSpark user community. It can be accessed here. Foundry Health Some product team members may engage with members of the community in this platform, but otherwise do not have direct involvement in topics of discussion or it’s use.
...
We provide access to a community ClinSpark development environment for our customers to review new & unreleased builds of ClinSpark, explore explore the latest features and proof of concepts, provide us with product feedback, and have a general area to collaborate with others in.
...
As a shared instance, please be respectful of community use. If there is question about any existing configurations or study setups, consider reaching out to someone at Foundry Healththe product team via service desk.
In general, the environment is provided with the following expectations & understanding:
Not subject to normal ClinSpark service level agreements
Owned and maintained by Foundry Healththe ClinSpark product team
Available for use by any existing Foundry Health customers or development partners
Not intended for any ‘production’ data; sensitive, PHI or other
The Volunteer database is expected to contain obscure/obfuscated data, and should otherwise not contain any ‘real’ volunteer data
The environment is subject to frequent deployments at an interval of Foundry Health our choosing
Build and configurations deployed may contain unreleased / new features that have not yet been formally tested
The database and configurations may be changed or ‘wiped’ at any time