Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

What are Service Acceptance Criteria (SAC)?

Service Acceptance Criteria (SAC) are used to assure that authored SNOMED CT content meets specific quality measures before the content can be promoted. The purpose of this is to ensure a specific level of quality is met at each promotion level. This in turn assures the quality of the content that is eventually promoted to the code system branch, with the benefit of minimising the quality checks required at that level (in general, the later the stage of the content release process, the greater the amount of work needed to correct any issues, so catching issues earlier in the process has many benefits).

SAC may be either automatic automated or manual. 

Automatic Automated SAC are checks which the system can sign off automatically without user intervention.

Manual SAC are checks that require sign-off via a particular user interaction, with that interaction governed by role-based access controls.

SAC may also be mandatory or optional.

Mandatory SAC block branch promotion until their required conditions are satisfied.

Optional SAC do not block promotion, but best practice would be to inform the Project Manager and/or Project Lead of reasons for promoting without the check being satisfied (an example may be a task-level spelling check, which might depend on the nature of the content being changed, and the availability of related spell-checking resources).

Info
titleService Acceptance Criteria and Authoring Acceptance Gateway Architecture (Authoring Platform)

Service Acceptance Criteria are components in a technical architecture solution which includes the Authoring Acceptance Gateway (AAG) and various data stores associated with acceptance and sign-off of content changes for promotion via AP tasks and projects, and also for the generation and packaging of SNOMED CT releases.

The following schematic illustrates the subset of this architecture directly related to AP features and their inter-relationships and dependencies (components relating to release preparation and packaging are omitted here for clarity, but are essential aspects of the overall technical architecture):

Gliffy Diagram
displayName AP Service Architecture: SAC & AAG
nameService Architecture - AAG - SAC
pagePin4

SAC are defined at the global level by users with the ADMIN role, as are their mapping to required RBAC roles. This is currently constrained as a technical support feature.

Globally defined SAC are then available as an options list to those with relevant permissions (set by RBAC role group definitions on the branch or its parents), to decide which to include in task-level or project-level gateway controls.

SAC are presented as checklist items in either the task details (for task level SAC) or project view (for project level SAC). The ability to modify the manual items to check them off via the AP user interface is a permission granted by the role assigned to each item in the SAC list. Task level manual SAC are usually available to all authors. Some project level manual SAC may also be available to all authors, but many will require additional permissions such as those for Project Managers or Project Leads to update (specific role mappings are set in the SAC global configuration definitions).

Some aspects of acceptance gateway controls are implicit in the AP branch promotion process - for instance diverged content branches cannot be promoted: each branch must be rebased from its immediate parent branch with all merge conflicts resolved before the branch can be promoted.

Info
titleAuthoring Acceptance Gateway 1: Task Level SAC examples


Excerpt
Early Visibility Notice if Required
Manual spell check
Review complete
RVF Report Clean



Info
titleAuthoring Acceptance Gateway 2: Project Level SAC examples


Excerpt
Project Documentation (TIG Editorial Guide) Complete
Project Lead (Peer reviewer): All Release Validation Reports Checked
Project Lead (Peer reviewer): Exceptions Checked and Signed off
Project Lead (Peer reviewer): Final Sign-Off
Project Manager: Signed Off Project as Ready to Promote
Relevant MRCM Changes Implemented
Report: Case Significance Clean
Report: Duplicate Terms Clean
Report: KPI Patterns Clean
Report: New Descriptions Clean
Report: Release Issues Clean
Report: Template Compliance Clean
Report: Validate Inactivations with Associations Clean
Validation Report Clean



Related How To... Guides

Content by Label
showLabelsfalse
showSpacefalse
cqllabel = "how-to" and label in ("RBAC","Role-Based-Access-Control","SAC","Service-Acceptance-Criteria") and space = currentSpace()

Further Reading

Project Branches, Task Branches and Rebasing

Role Based Access Control (RBAC)