Publishing

Publish your own forms, templates and skills to the Marketplace and manage what you have released.

Publishing is for sharing content with other practices on the Marketplace. It is separate from your own practice's Library: nothing you write in the Library reaches the Marketplace unless you publish it here. Your role in the publisher is separate from your role in a practice.

Get publisher access

Publishing appears in the sidebar, under Manage (or on its own if you have no practice), when you belong to a publisher, have applied, or have an invitation. Otherwise you can do one of two things:

Accept an invitation. An owner of a publisher invites you by email. Choose Accept. You can belong to one publisher at a time.
Apply. Open the Apply to publish page at /apply-to-publish, enter your name, Publisher name and Publisher handle, describe what you will publish and where it comes from, choose Countries, and choose Send application. Salisan reads every application and replies by email.

Owners invite people and choose their roles on the Team page. Editors write, submit and take content down. A publisher always needs at least one owner.

Submit a release

Open Publishing, then Catalog, and choose New content. Pick Form, Report template, Email template or Skill.
Write and preview the content. Complete titles, descriptions and the translations your countries need.
If the content builds on someone else's work, add it under Sources and choose Confirm source. The source record holds the rights holder, the license and whether practices may copy the content. An unconfirmed source blocks publishing.
Choose Publish. Under Available in, pick at least one country, check the Source, and add a Release note.
Choose the button that reads Submit and the version number for review.

Every release goes to review first, and Salisan's own releases too. Nothing is live on the Marketplace until it is approved. When it is, practices in the countries you chose can find and install it. Check the countries and language completeness before you submit.

In the Catalog, the In review tab shows what is waiting. The tiles above the list (Live, In review and Drafts) are filters: choose one to show only those items, and choose it again, or the filter chip under the tabs, to clear it. The Installs and Responses tiles are readouts only. If the status reads Changes requested, fix the issues the reviewer lists and submit again.

Release an update

When a version is already live, the dialog asks what kind of change this is.

Update is for wording, typos, translations or a new language. It applies automatically to every practice on that version, with no review by the practice.
New version is for a change in structure. Practices review it before they switch, and analytics keeps the answers of each version apart.

To publish an update you must confirm that the meaning of every question is unchanged. If it changed, publish a new version instead. Responses already collected keep the structure they were collected under.

Take content down

Choose Take down… on a Catalog row. The dialog shows how many times it was installed and how many are in use now. A version waiting for review is cancelled too. Pick one:

Unlist stops new installs. Practices keep using what they installed, and you can choose List again later.
Recall is for unsafe content. It turns off every installed copy and cannot be undone. You must give a reason that practices will see, saying what is wrong and what to use instead.

Collections that include the item stay live without it. A collection left with fewer than two live items is unlisted.

Collections and analytics

A collection is a themed set that practices can install together. It is a starting point, not a subscription. Under Collections, choose New collection, add a title and content from your catalog, pick the countries, and choose Submit for review. Saving changes to a live collection sends it back to review, and it leaves the Marketplace until it is approved again.

Choose Analytics on a Catalog row to see installs, use, responses, countries and version adoption. The numbers are aggregated and do not identify a practice or a patient.