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

Harmonize CP EHSEPDBEP-222 / AuditEvent profiling #190

Open
oliveregger opened this issue Jun 11, 2024 · 10 comments
Open

Harmonize CP EHSEPDBEP-222 / AuditEvent profiling #190

oliveregger opened this issue Jun 11, 2024 · 10 comments
Assignees

Comments

@oliveregger
Copy link
Collaborator

EHSEPDBEP-222 Das Change Proposal sagt:

ParticipantObjectTypeCode M “2” (system object)
ParticipantObjectTypeCodeRole M “26” (processing element)
ParticipantObjectDataLifeCycle U not specialized

Aktuell haben wir aber die folgende Abbildung verwendet:

1). https://fhir.ch/ig/ch-epr-fhir/StructureDefinition-ch-epr-fhir-auditevent.html 4 (Other) anstelle von 2 (system object). MHD verwendet die 2 schon im Slicing und das ist besetzt, siehe https://profiles.ihe.net/ITI/MHD/4.2.2/StructureDefinition-IHE.MHD.ProvideBundle.Audit.Source.html).
2.) Wir finden den Code nirgendwo für “26” (processing element), woher kommt der? In https://terminology.hl7.org/5.5.0/CodeSystem-object-role.html habe ich nicht gefunden.

@unixoid
Copy link
Collaborator

unixoid commented Jun 11, 2024

Code "26" kommt aus DICOM, siehe https://dicom.nema.org/medical/dicom/current/output/chtml/part15/sect_A.5.html, Tabelle A.5.1.2.2-1.

@dkotlaris
Copy link

Change Proposal zu EHSEPDBEP-222 angepasst:
ParticipantObjectTypeCode von “2” (system object) auf "4" (other) geändert.

@oliveregger
Copy link
Collaborator Author

DK: Trace Context: Bei Retrieve ATNA Audit Event [ITI-81] beim CH ATC-Profil wurde dieser noch nicht analog zu den Transaktionen der anderen Profile ergänzt. Sehe ich das richtig?

@oliveregger oliveregger self-assigned this Jun 18, 2024
@oliveregger
Copy link
Collaborator Author

15.8: General Discussion: Do we want to the DICOM way (this approach) or do we wan't to go the BALP approach.

@dkotlaris
Copy link

I take it up for our next expert group meeting on 21.08.2024.

@oliveregger
Copy link
Collaborator Author

@dkotlaris we need to provide the examples first, can we schedule it for a following meeting?

@dkotlaris
Copy link

Yes, of course.

@dkotlaris
Copy link

dkotlaris commented Nov 1, 2024

AG Steuerung Weiterentwicklung rejected the extension of the W3C Trace Context in the EPR on October 24, 2024.
That means, the elaborated solution for the ordinance and the ATC and EPR FHIR IG cannot be integrated in release 2025 and the already made changes have to reverted.

@oliveregger
Copy link
Collaborator Author

For EPR FHIR the tracecontext will still be possible to be added to the transactions and auditevents.

@oliveregger
Copy link
Collaborator Author

Concerning the 26 code we opened an issue on terminology.fhir.org: UP-621
Add codes 25, 26 to https://terminology.hl7.org/CodeSystem-object-role.html

and opened the discussion on zulip too

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants