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.

Sign up for GitHub

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

Jump to bottom

HTTP return anpassen #308

Closed
1 task
f-peverali opened this issue Oct 25, 2023 · 1 comment · Fixed by #354
Closed
1 task

HTTP return anpassen #308

f-peverali opened this issue Oct 25, 2023 · 1 comment · Fixed by #354
Labels
enhancement New feature or request

Comments

@f-peverali
Copy link
Contributor

f-peverali commented Oct 25, 2023 •
edited
Loading

spec-ISiK-Basismodul/ImplementationGuide/markdown/BerichtSubsystem/BerichtSubsystem_Interaktionen.md

Line 13 in 6e2131d

Falls die im Dokumenten-Bundle enthaltene Patient-Ressource und/oder Encounter-Ressource nicht anhand der Business-Identifier oder anderer Matching-Kriterien im empfangenden System gefunden werden kann (d.h. der Patient oder der Encounter existiert im empfangenden System noch nicht), MUSS als Antwort der HTTP Status Code "422 - Unprocessable Entity" zurückgegeben werden. Im Body der Response ist eine OperationOutcome zurückzugeben, welche ein Issue mit dem Verweis auf die nicht auflösbare Referenz enthält. Zur Kodierung von OperationOutcome.issue.code MUSS als Code ["processing"](https://hl7.org/fhir/R4/codesystem-issue-type.html) verwendet werden.

  • Die Vorgaben für die HTTP Return Messages in der Basis sollten (analog zur Änderung in der Terminplanung, vergleiche hier: HTTP Code definieren? spec-ISiK-Terminplanung#121), sowohl syntaktische als auch semantische Errors abdecken.
  • Auch die HTTP 2xx Codes sollten kohärent sein.
  • Ggf. auch an anderen stellen in der Basis zu lösen
  • Die bitte als PR für einen TC ausweisen und nicht direkt in main mergen

Tasks
Preview Give feedback
@f-peverali f-peverali added the enhancement New feature or request label Oct 25, 2023
@f-peverali f-peverali moved this from Todo to Backlog in ISiK/ISiP Project Board Oct 25, 2023
@f-peverali f-peverali mentioned this issue Oct 25, 2023
Closed
@f-peverali f-peverali moved this from Backlog to Todo in ISiK/ISiP Project Board Oct 31, 2023
@f-peverali f-peverali mentioned this issue Oct 31, 2023
Closed
@f-peverali
Copy link
Contributor Author

umsetzen mit #312

@f-peverali f-peverali moved this from Todo to Backlog in ISiK/ISiP Project Board Nov 20, 2023
f-peverali added a commit that referenced this issue Jan 12, 2024
@f-peverali
update HTTP response requirement #308
176ca63
@f-peverali f-peverali linked a pull request Jan 12, 2024 that will close this issue
update HTTP response requirement #308 #354
Merged
alexzautke added a commit that referenced this issue Jan 12, 2024
@alexzautke
Merge pull request #354 from gematik/feature/HTTP-response-harmonizat…
46499ba 
…ion-PTData-704

update HTTP response requirement #308
f-peverali added a commit that referenced this issue Jan 15, 2024
@f-peverali @alexzautke @MaxMTheilig
TC 3.0.3 - update HTTP response requirement #308 (#353)
543f959 
* init TC 3.0.3

* update HTTP response requirement #308

* Update ImplementationGuide/markdown/UebergreifendeFestlegungen/UebergreifendeFestlegungen_Rest.md

* Update ImplementationGuide/markdown/UebergreifendeFestlegungen/UebergreifendeFestlegungen_Rest.md

* Feature/devops automation (#355)

* initial devcontainer added

* enhancement of workflow files

* restrcuted image folders

* auto-generated diagrams by GitHub Action after source code change

Co-Authored-By: MaxMTheilig <[email protected]>

* update releasenotes

* update version

* auto-generated FHIR files by GitHub Actions (CI FSH to FHIR Validation)

---------

Co-authored-by: Alexander Zautke <[email protected]>
Co-authored-by: Max Theilig <[email protected]>
Co-authored-by: MaxMTheilig <[email protected]>
Co-authored-by: f-peverali <[email protected]>
@github-project-automation github-project-automation bot moved this from Backlog to Done in ISiK/ISiP Project Board Apr 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
ISiK/ISiP Project Board
Status: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

update HTTP response requirement #308 gematik/spec-ISiK-Basismodul
1 participant
@f-peverali