Approval
The first step in release is approving new/modified content for publication once the authoring process is complete.
Depending on your deployment model, different approaches are required
The security model of Ontoserver must be used to control approval and visibility of content to read-only users. The required approach is described in Single read/write server deployment.
For deployments involving a read/write Ontoserver instance for authoring and one or more read-only Ontoserver instances for distribution and use of the content, this section is very relevant. The following sections describe how approval is achieved for FHIR resources and the special case of SNOMED CT and LOINC indexes in this case.
Content is published by the Production Ontoserver instance pulling content from the Authoring server’s syndication feed.
For a resource to appear in the Authoring server’s syndication feed requires a user with approval rights to set the syndication status of a resource to “true”. Until this is done, a resource will not be available in the Authoring server’s syndication feed, and therefore cannot be imported into the Production server for downstream use. This is how draft additions and changes are kept private until they are assessed as ready for use.
To set the set the syndication status on resources refer to the processes defined in the Approval processes section.
Under this model, authors develop content on the Authoring terminology server. Content is approved by users with an Approver role using the Approval processes, which changes the state of the Authoring server’s syndication feed to include or omit the resource depending upon the approver’s decision.
Approval processes for FHIR resources for publication in the authoring server
Approving resources in the Authoring server is a matter of setting their syndication status to true which will ensure that Ontoserver includes the resource in its syndication feed.
The API for automating this can be found in Ontoserver’s documentation, however this function is exposed in both Snapper and OntoCommand (the administrative user interface).
Approve indexes for publication in the authoring server
Unlike other FHIR CodeSystems, CodeSystems for SNOMED CT and LOINC backed by Ontoserver indexes cannot be approved for syndication using Snapper.
Instead OntoCommand must be used similarly to the process described above.
Content can be added directly into Ontoserver