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

Open Issue 7: x-request-id #46

Open
JohnMoehrke opened this issue Apr 27, 2022 · 4 comments
Open

Open Issue 7: x-request-id #46

JohnMoehrke opened this issue Apr 27, 2022 · 4 comments
Labels
Open-Issue Issues related to open-issues in published specification.

Comments

@JohnMoehrke
Copy link
Contributor

X-Request-Id header – I explained this only inside of the RESTful section, but it is applicable anywhere that X-Request-Id is used. X-Reqeust-Id is profiled differently than the example given in the FHIR core specification. Specifically there is a entity type defined here to enable slicing, where the example in FHIR core uses both type (job) and role (stream) which is harder to slice. I did not make this a standalone section because it is simply too small.
X-Request-Id vs TraceId – I added X-Request-Id profiling. I did not add TraceId, as I am not as aware of what this is. It seems very similar, unclear if it is different or the same thing. The modeling of TraceId that is in the FHIR Core is a bit different than I modeled X-Request-Id here. TraceId example in core is a .entity.type #21 “Job”, with a .entity.what.identifier.type #TraceId. Where as for X-Request-Id I followed the example that Grahame indicted his server supports today for X-Request-Id. I welcome comment, as I am not an expert TraceId nor X-Reqeust-Id.
@JohnMoehrke JohnMoehrke added the discussion needing committee discussion label Apr 27, 2022
@JohnMoehrke
Copy link
Contributor Author

we got no comments, but I did hear informally that there are some other similar things

@JohnMoehrke JohnMoehrke added Open-Issue Issues related to open-issues in published specification. and removed discussion needing committee discussion labels Apr 27, 2022
@JohnMoehrke
Copy link
Contributor Author

leave an open issue so that others can comment on need

@JohnMoehrke
Copy link
Contributor Author

might this be similar https://www.w3.org/TR/trace-context/

@JohnMoehrke
Copy link
Contributor Author

https://chat.fhir.org/#narrow/stream/179166-implementers/topic/AuditEvent.20and.20W3C.20Trace.20Context

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Open-Issue Issues related to open-issues in published specification.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@JohnMoehrke