DRAFT SMART Guidelines L3 SOP
0.2.1 - CI Build International flag

DRAFT SMART Guidelines L3 SOP, published by TBD. This is not an authorized publication; it is the continuous build for version 0.2.1). This version is based on the current content of https://github.com/DigitalSQR/smart-ig-starter-kit and changes regularly. See the Directory of published versions

User Scenarios

Scenarios are uniquely identified “example stories” that describe how the system is expected to behave in a relatively concrete scenario.

Each Persona is defined by the following data:

Scenarioidentifier[SG] 1..*status 1..1name 1..1title 1..1description 1..1actor 1..*step 1..1initiator 0..1receiver 0..1activity 0..1description 0..1

Inputs:

  • L2 scenarios in narrative form

Outputs:

  • ExampleScenarios in input/scenarios
  • One FSH file per ExampleScenario in input/fsh/scenarios

Activities:


  • Check input scenarios - the L2 should contain identifiable, well-defined and well-delimited scenario descriptions. these should be rather concrete - i.e. not high abstractions, but concrete to a specific context.
  • Develop ExampleScenario resources
TO DO: we should have SUSHI RuleSets for this resource
TO DO: This deserves some data generation feature.

Output Criteria / Definition of Done:

  • Each User Scenario in the L2 should be covered by one or more ExampleScenarios
    • At least the “normal” flow shall be covered by an example scenario
  • ExampleScenarios should reference the example instances from the other resources (see profiles, decision tables, scheduling logic, forms, indicators)
  • ExampleScenarios should be validated by the publisher (i.e. no QA issues)
  • ExampleScenarios should be reviewed by the L2 author

Change tracking

ExampleScenarios are not normative material. Change tracking shall follow the general guidance.

Tooling

Tool Usage Doc
Sushi New ExampleScenarios can be created in FSH syntax HL7 Spec
Sushi Documentation

Informative examples

Known issues and dependencies