Skip to content

User Story 2022_088

As a Participant, I want to avoid missteps by maintaining knowledge of the state of case and what options are available.

Superseded by: 2026_011, 2026_014, 2026_018, 2026_019, 2026_023, 2026_029, 2026_030, 2026_031, 2026_034, 2026_036, 2026_037, 2026_038, 2026_039, 2026_040, 2026_041, 2026_042, 2026_043, 2026_044, 2026_045, 2026_046, 2026_047, 2026_048, 2026_049, 2026_050, 2026_051, 2026_052, 2026_053, 2026_054, 2026_055, 2026_056, 2026_057, 2026_058, 2026_059, 2026_060, 2026_061, 2026_062, 2026_063, 2026_064, 2026_065, 2026_066, 2026_067, 2026_068.

This story was split into narrower stories in #4516, and every requirement that cited it now cites the narrowest replacement that states its need. Its ID is not reused.

Notes

The state-change messaging orientation of the protocol provides Participants the opportunity to track the changes as they happen. The GI message type permits Participants to inquire about and resolve loss-of-sync issues.

Metadata

Following is additional information compiled from our original design materials. We are including it here for future reference and traceability.


  • Potential future process or service: nan
  • Roles: Participant
  • Phases: Any
  • Categories: Policy, Monitoring (incl. IR), Infrastructure

  • File: story_2022_088.md
  • Original ID: 113.0
  • 2022 Whitepaper ID: CVD-API-122-113