SMART Guidelines L3 SOP
1.1.0 - ci-build International flag

SMART Guidelines L3 SOP, published by WHO. This guide is not an authorized publication; it is the continuous build for version 1.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/WorldHealthOrganization/smart-ig-starter-kit and changes regularly. See the Directory of published versions

Business Processes

Business processes are structured into FHIR PlanDefinitions. This can be used to fully structure and define business business processes like what’s done in BPM+, BPMN, etc. but most commonly the main goal is to keep inventory of the business processes as well as their the dependencies between processes, processes and actors, etc.

The L3 author must ensure there is a PlanDefinition for each Business Process mentioned in the L2.

The data required to be captured for each Business Process is:

BusinessProcessidentifier 1..*status 1..1name 1..1title 1..1description 1..1diagram_source 1..1Data needs forbusiness processes(seelegend)

Inputs

  • L2 Business Processes
  • Business Process Repository
  • L2 DAK

Outputs

  • Proposed new Business Process definitions as PlanDefinitions.

Activities


Summary: From the L2 Business Process, the L3 author creates a PlanDefinition to illustrate the business process.

Output Criteria / Definition of Done

  • Each Business Process SHALL have a corresponding PlanDefinition
  • Each PlanDefinition representing a Business Process SHALL conform to the CRMIShareablePlanDefinition profile
  • Each active published PlanDefinition representing a Business Process SHALL conform to the CRMIPublishablePlanDefinition profile
  • Each PlanDefinition representing a Business Process SHALL have:
    • name: A computable name for the process
    • title: A short, user-friendly description of the process
    • type: workflow-definition
    • description: A detailed description of the process
  • For each “node” in the business process representing an activity to be performed, the PlanDefinition should have an action element:
    • title: A short, user-friendly description of the activity
    • description: A more detailed description of the activity
    • participant: Identify the expected participants in the activity, identified by the Persona
  • Connect the nodes as appropriate to indicate process flow
    • relatedAction:
      • actionId: a reference to the related activity
      • relationship: the type of relationship (note that the before-start relationship should be favored, and that relationships should only be characterized in one direction)

For more information, see the Mapping and Other Formalisms topic in the Clinical Practice Guidelines implementation guide.

Change tracking

As with all FHIR Conformance resources, change management is critical. Do not set the version element of PlanDefinitions defined in the SMART Guideline, the version element will be set by the publication process. See the versioning topic for more information on change management.

Tooling

Informative examples

Known issues and dependencies