|
|
|
Participants: Katinka, Emil, Tjard, Asif, Johannes, Jan
|
|
|
|
|
|
|
|
* Corona politics
|
|
|
|
* Emergency section guidance by Anna
|
|
|
|
* Present our experiences
|
|
|
|
* Different waiting rooms, one with beds
|
|
|
|
* You do not see every other waiting person
|
|
|
|
* Probable issue for patient satisfaction
|
|
|
|
* Impression nothing is happening
|
|
|
|
* Different severity levels
|
|
|
|
* Lines on the floors for catastrophic events
|
|
|
|
* Reserved bed room
|
|
|
|
* Specific room for aggressive patients
|
|
|
|
* Treatment of Corona patients (whether their issue is related or not)
|
|
|
|
* Shock room needs 10 people to be operated
|
|
|
|
* Restrained resources
|
|
|
|
* Lots of bottlenecks
|
|
|
|
* But they are well organized
|
|
|
|
* Huge variance in the care time a patient gets
|
|
|
|
* Leads to long cues
|
|
|
|
* Possible to reduce the variance?
|
|
|
|
* Documentation
|
|
|
|
* Lots of communication with fire department
|
|
|
|
* to determine the Hospital to patient gets to
|
|
|
|
* Also Postmortems
|
|
|
|
* Webserver
|
|
|
|
* Probably not needed
|
|
|
|
* As the prototype is just html/css/js
|
|
|
|
* Userpage with Unix ACLs will suffice for collaboration
|
|
|
|
* Maybe Github pages or Gitlab pages
|
|
|
|
* Prototype
|
|
|
|
* Does (probably) not need code to be triggered on server by client
|
|
|
|
* Has to be extended to match the agreed-on designs
|
|
|
|
* Accessibility
|
|
|
|
* HTML can be made accessible with low effort
|
|
|
|
* Language
|
|
|
|
* Chosen by Javascript part
|
|
|
|
* XML file containing all the strings
|
|
|
|
* templates can be compiled statically
|
|
|
|
* Presentation
|
|
|
|
* First date in January 4th
|
|
|
|
* Present a schedule
|
|
|
|
* Way of thinking
|
|
|
|
* Planning, planning, planning
|
|
|
|
* Planning backwards: By when does this task dependency has to be done?
|
|
|
|
* Find a way of planning even before the texts are there
|
|
|
|
* "No Typo3" incident
|
|
|
|
* Okay
|
|
|
|
* Tasks
|
|
|
|
* Upload prototype (Asif)
|
|
|
|
* Extend the designs
|
|
|
|
* One ticket per use case
|
|
|
|
* Add Language support
|
|
|
|
* Evaluate dynamic translator support
|
|
|
|
* Ask on Friday if dynamic content is needed
|
|
|
|
* Only static text?
|
|
|
|
* API: Only internally, right?
|
|
|
|
* Propose suggestions
|
|
|
|
* Weekly updates of the numbers or so
|
|
|
|
* Expose on endpoint?
|
|
|
|
* More content: "Last year, the ED had xx patients"-like.
|
|
|
|
* Introduction with general stats to the website
|
|
|
|
* Description of the ED
|
|
|
|
* Which information can be pulled from where?
|
|
|
|
* Clarify with Marlene and Tom, who write the texts |
|
|
|
\ No newline at end of file |
