Versions Compared

Old Version 20

changes.mady.by.user Erik Nielsen

Saved on

compared with

New Version 21

changes.mady.by.user Erik Nielsen

Saved on

Key

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

...

  • recipient = Patient reference

  • category = <depending on situation>

  • reasonCode = <depending on situation>

  • episodeOfCare = <depending on situation>

  • basedOn = <depending on situation>

  • priority = <depending on situation>

Situation

Created by Default

Opt-in Supported

Opt-out Supported

Payload and Medium Overridable

Element category

Element reasonCode

Element episodeOfCare

Element basedOn

Element priority

Unexpected measurement submitted

No

Yes

No

Yes

message

UnexpectedMeasuringResolving

ServiceRequest reference

routine

Missing measurement determined

No

Yes

No

Yes

message

MissingMeasurementResolving

ServiceRequest reference

routine

Reminder to submit measurement (about to be created)

Yes

No

Yes

No

advice

EpisodeOfCare reference

Communication created by triage (or other infrastructure rules)

No

Yes

No

Yes

depends on rule

depends on rule

ServiceRequest reference

depends on rule

EpisodeOfCare created/changed (in team, status, scheduledStatus or scheduledTeam)

Yes

No

Yes

No

message

EpisodeOfCare reference

CarePlan created/changed (in careTeam, status, scheduledStatus or scheduledTeam)

Yes

No

Yes

No

message

EpisodeOfCare reference

Reminder about appointment

Yes

No

No

No

Message category Communication with Patient as recipient created

Yes

No

No

No

Info

The paragraph below reflects behavior as of eHealth Infrastructure Release 14.

Situation

Created by Default

Opt-in Supported

Opt-out Supported

Payload and Medium Overridable

Element category

Element reasonCode

Element episodeOfCare

Element basedOn

Element priority

Unexpected measurement submitted

No

Yes

No

Yes

notification

UnexpectedMeasuringResolving

ServiceRequest reference

Missing measurement determined

No

Yes

No

Yes

notification

MissingMeasurementResolving

ServiceRequest reference

Reminder to submit measurement (about to be created)

Yes

No

Yes

Yes

advice

ReminderSubmitMeasurement

EpisodeOfCare reference

Communication created by triage (or other infrastructure rules)

No

Yes

No

Yes

notification

Depends on rule

ServiceRequest reference

Depends on rule

EpisodeOfCare created

No

Yes

No

Yes

notification

EpisodeOfCareCreated

EpisodeOfCare changed (in team, status, scheduledStatus or scheduledTeam)

No

Yes

No

Yes

notification

EpisodeOfCareCareTeamChange , EpisodeOfCareScheduledCareTeamChange , EpisodeOfCareStatusChange or EpisodeOfCareScheduledStatusChange

EpisodeOfCare reference

CarePlan created/changed (in careTeam, status, scheduledStatus or scheduledTeam)

No

Yes

No

Yes

notification

CarePlanCreated,CarePlanCareTeamChange , CarePlanScheduledCareTeamChange , CarePlanStatusChange orCarePlanScheduledStatusChange

EpisodeOfCare reference

Reminder about appointment

Yes

No

Yes

Yes

advice

AppointmentNotification or VideoAppointmentNotificationdepending on appointment type

EpisodeOfCare reference

Automated creation of medium nemsms Communication when Communication with category message and Patient as recipient created

No

Yes

No

Only medium=nemsms possible

message

Same as ehealth-message (or left empty to match all ehealth-message reasonCodes)

EpisodeOfCare reference

...

  • recipient = CareTeam reference

  • category = <depending on situation>

  • reasonCode = <depending on situation>

  • episodeOfCare = <depending on situation>

  • basedOn = <depending on situation>

  • priority = <depending on situation>

...

Situation

Created by Default

Opt-in Supported

Opt-out Supported

Payload and Medium Overridable

Element category

Element reasonCode

Element episodeOfCare

Element basedOn

Element priority

Unexpected measurement submitted

No

Yes

No

No

notification

UnexpectedMeasuringResolving

ServiceRequest reference

Missing measurement determined

Yes

No

Yes

No

notification

MissingMeasurementResolving

ServiceRequest reference

Communication created by triage (or other infrastructure rules)

Yes

No

Yes

No

depends on rule

depends on rule

ServiceRequest reference

depends on rule

EpisodeOfCare created

Yes

No

Yes

No

notification

EpisodeOfCareCreated

EpisodeOfCare changed (in team, status, scheduledStatus or scheduledTeam)

Yes

No

Yes

No

notification

EpisodeOfCareCareTeamChange , EpisodeOfCareScheduledCareTeamChange , EpisodeOfCareStatusChange or EpisodeOfCareScheduledStatusChange

EpisodeOfCare reference

CarePlan created/changed (in careTeam, status, scheduledStatus or scheduledTeam)

Yes

No

Yes

No

notification

CarePlanCreated,CarePlanCareTeamChange , CarePlanScheduledCareTeamChange , CarePlanStatusChange orCarePlanScheduledStatusChange

EpisodeOfCare reference

Reminder about appointment

No

Yes

No

Only payload

advice

AppointmentNotification or VideoAppointmentNotificationdepending on appointment type

EpisodeOfCare reference

Scope of the Message Creation Control

Info

The paragraphs below reflects behavior as of eHealth Infrastructure Release 14.

Search Algorithms for CommunicationRequest applied in the Infrastructure

...

Ending a Message Creation Control

...

To remove the effect of a CommunicationRequest, perform a CommunicationRequest Update and set the status to completed. If the CommunicationRequest uses occurrencePeriod and has no occurrencePeriod.end, it would be consistent to set it to time of completing the CommunicationRequest.