You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
The text was updated successfully, but these errors were encountered:
Section Number
SDPi TF-1C
Priority
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.
The text was updated successfully, but these errors were encountered: