Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-43903

Scenario process steps should reference actors

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R6
    • FHIR Infrastructure
    • ExampleScenario
    • Hide

      This is a pattern used in quite a few other resources.  Even where ActorDefinitions are referenced by an ExampleScenario (which will be supported in R6), these will still be defined at the top and individual exchanges will point via key, not to the ActorDefinition itself, because there is ExampleScenario-specific actor information that comes into play.

      Show
      This is a pattern used in quite a few other resources.  Even where ActorDefinitions are referenced by an ExampleScenario (which will be supported in R6), these will still be defined at the top and individual exchanges will point via key, not to the ActorDefinition itself, because there is ExampleScenario-specific actor information that comes into play.
    • John Hatem/Reinhard Egelkraut: 6-0-0

    Description

      Currently, ExampleScenario.process.step.operation.initiator and receiver are string datatypes. The definitions have a comment:

      This must either be the 'key' of one of the actors defined in this scenario or the special keyword 'OTHER' if the initiator is not one of the actors defined for the scenario. (Multiple references to 'OTHER' don't necessarily indicate the same actor.)

      This is not a very typical way to do references, and I worry about implementation hurdles.

      Attachments

        Activity

          People

            Unassigned Unassigned
            ginocanessa Gino Canessa
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: