Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Use Case(s) related to Lost Connection Scenarios #296

Open
ToddCooper opened this issue Jun 6, 2024 · 1 comment
Open

Add Use Case(s) related to Lost Connection Scenarios #296

ToddCooper opened this issue Jun 6, 2024 · 1 comment
Assignees
Labels
Comment Review Comment of some sort from somewhere sometime Volume 1 Volume 1 contents

Comments

@ToddCooper
Copy link
Collaborator

Section Number

SDPi TF-1C

Priority

  • Medium: Significant issue or clarification. Requires discussion, but should not lead to long debate.

Issue

For example, when you have a Wi-Fi connection on a patient-to-patient (e.g., spot check monitors, infusion pumps, etc.), at reconnection, how to re-establish patient & location contexts, MDIB changes, etc. NOTE: these would be alternate scenarios for a use case to establish requirements, then detail technical approach (TF-1 then TF-2); perhaps Gherkin formalization will help. Mobile (in hospital) including telemetry. Intent here is that the connection is normally available but can drop depending on environment conditions. Note: Consider "History Service" alternative.

See Topic: MDIB Update Management with Intermittent Connection for background information.

Proposed Change

Add one or more use cases to TF-1C to help identify the challenges and requirements toward connections that are lost and recovered ("intermittent") and how to best manage information coherence.

@ToddCooper ToddCooper added Comment Review Comment of some sort from somewhere sometime Comment NEW A submitted comment waiting to be reviewed and dispositioned labels Jun 6, 2024
@ToddCooper ToddCooper added this to the SDPi 2.0 review milestone Jun 6, 2024
@ToddCooper ToddCooper added Volume 1 Volume 1 contents and removed Comment NEW A submitted comment waiting to be reviewed and dispositioned labels Jun 14, 2024
@JavierEspina
Copy link
Collaborator

@ToddCooper - is this something that can be pushed to 2.1?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Comment Review Comment of some sort from somewhere sometime Volume 1 Volume 1 contents
Projects
Status: New issues
Development

No branches or pull requests

3 participants