Versions Compared

Key

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

...

View and ActionGuidance are created and updated through Basic Create and Basic Update, respectively, using the profiles ehealth-actionguidance and ehealth-view, respectively.

Info

Later finding appropriate View and ActionGuidance resources depends on the quality and granularity with which the View and ActionGuidance elements are populated when created/updated. Consequently, effort should be made to ensure these elements are populated.

Filtering applied on finding appropriate View and ActionGuidance could involve the following elements of View and ActionGuidance:

  • useContext

  • ehealth-intendedAudience

  • ehealth-recommendation

  • status

  • modifier-role

Possibly, the following elements (and others) could be used as well:

  • title

  • description

  • version

Since both View and ActionGuidance are instances of the Basic resource, it will often be useful to use either code or profile to distinguish between them.

An ActionGuidance should reference one or more questionnaires through the Both ActionGuidance and View can reference a number of resources which they are intended to be used with, through elements ehealth-actionguidance-for element, even that the element is optional. A View should reference one or more questionnaires through the and ehealth-view-for element, even that the element is optional, respectively. Currently, such resources are expected to be of type Questionnaire.

Releasing a View or ActionGuidance

...

Info

The contents of View or ActionGuidance cannot be changed once having status set to active. Please be aware sure to specify ehealth-view-for or ehealth-actionguidance-for before activating. Administrative fields such as intendedAudience, modifier-role, recommendation etc. and useContext can still be updated.

Retiring a View or ActionGuidance

...