Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Feature/rollback stufe 3 interactions encounter+patient ptdata 1419 #226
base: TC_3.0.5
Are you sure you want to change the base?
Feature/rollback stufe 3 interactions encounter+patient ptdata 1419 #226
Changes from 4 commits
27aaa17
92e2798
3668de0
b049f58
290527b
907db03
1ec2e1b
8e0d93a
2904c88
f07d00d
9284ff8
d6106f9
28213b1
a0e2e83
1e9877e
1212bd0
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Während der Überlegung zum Entfernen der Suchparamter waren zwei Architekturen angenommen worden:
Architektur A - Integrierte Umgebung: Wir haben ein patientenführendes System (Basis -Server), das alleinig ISiK-Patienteninstanzen (und Encounter) verwaltet
Architektur B - geteilte Patienten (und -Encounter) Verwaltung: Basis-Server und DMS persistieren voneinander unabhängig ISiK-Patienten-Instanzen
Nachträglich erscheint Architektur A als nicht der Realität in KH-Umgebungen entsprechend - womöglich auch nicht als wünschenswert da eine autonomie der Datenhaltung der verschiedenen Systeme auch bei Ausfällen ein Sicherheits-Feature darstellt.
Es stimmt daher NICHT, dass das DMS selbst keine Abfrage auf eine Patienten-Instanz erfüllen muss - sondern lediglich in der Lage sein SOLL/MUSS (dies nicht geprüft) die "referentielle Integrität" zu prüfen (ggf. noch zu forwarden) durch eine Anfrage an den Basis-Server.
Es muss dagegen angenommen werden, dass ein DMS auch immer Patienter- und Encounter-Abfragen (zumindest zur Herstellung der Ressourcen-Kontexte) ermöglichen muss.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
question: wäre es nicht im Sinne der Wartbarkeit die Begründung hier direkt im CpS zu dokumentieren? wie könnte man das machen?
suggestion: @simoneOnFhir könntest du hier ggf. noch einen Vorschlag machen