Stream: fhir/infrastructure-wg
Topic: Some new features might be implemented in R5
Thomas Zhou (Apr 06 2022 at 21:30):
1 . The security label can be applied to the elements’ layer rather than resources.
For example, the consent of the owner of the health information only applies to the part of the CONDITION resource instead of the entire resource.
2. A separate triage tag can be specified out of the meta.tags for priority and time sensitivity of patient safety resource information. This triage tag can enable the system to push the information to the registered endpoints instead of waiting for the pull.
3. A guideline should provide suggestions on the number of reference layers to leverage smooth message exchanges without triggering a storm.
Lloyd McKenzie (Apr 06 2022 at 21:41):
If you want to label individual data elements, you'll need an extension. However, in practice, managing filtering at a data element level is very difficult (e.g. consider narrative). So be very sure you want to go down this path. And don't expect it to be widely supported.
Ward Weistra (Apr 07 2022 at 13:12):
Note that this is a duplicate post with https://chat.fhir.org/#narrow/stream/179160-social/topic/Three.20proposals.20are.20raised.20here.20for.20discussion.20for.20the.20FHIR
@Thomas Zhou Please don't ask the same question in multiple places because it will lead to people answering it multiple times, taking up more valuable volunteer time than needed. Please see the FHIR Rules for asking questions here: https://confluence.hl7.org/display/FHIR/FHIR+Rules+for+Asking+Questions
Thomas Zhou (Apr 07 2022 at 18:18):
I am sorry for my multiple posts.
Thomas Zhou (Apr 12 2022 at 15:58):
As suggested, I have created two FHIR tickets on the JIRA.
1. To provide a triage tag for each event resource with ticket number FHIR-36743
2. To provide a best-practice guide on the reference hop limit in use-case implementations with ticket number FHIR-36744
Please take a look and provide your valuable comments.
Josh Mandel (Apr 12 2022 at 16:00):
Thanks for these submission! Reading through the two Jira issues, I'm concerned that it's not entirely clear what changes you are asking for. Any chance you can update these issues with specific proposed changes to the language or content in the FHIR spec? e.g., "On this page of the spec, in this section, I would like to make the following changes..." -- this kind of specificity makes it much more likely that the FHIR Infrastructure Workgroup will be able to give your ideas full consideration.
Thomas Zhou (Apr 12 2022 at 18:18):
Thank you for the comments. I will proceed with the suggestions.
Last updated: Apr 12 2022 at 19:14 UTC
