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

NPFS_012: profile tagging #6

Open
apinton-Arsenal opened this issue Jun 1, 2023 · 1 comment
Open

NPFS_012: profile tagging #6

apinton-Arsenal opened this issue Jun 1, 2023 · 1 comment
Labels
open issue Open Issue mentioned in the Implementation Guide

Comments

@apinton-Arsenal
Copy link
Contributor

This document does not require the use of profile tags to identify compliant resources. Use of profile tags will also allow the File Consumer to search just for resources that matches this profile in a FHIR Server that store different types of resources. Readers are required to provide feedback on this topic.
@JohnMoehrke
Copy link
Contributor

profile tagging should not be used for searching. The elements of the DocumentReference are sufficient to find what any client needs to find. If they are not sufficient, then the NPFS constraints need to be improved.

@apinton-Arsenal apinton-Arsenal changed the title NPFS_012 NPFS_012: Profile tagging Jul 7, 2023
@apinton-Arsenal apinton-Arsenal changed the title NPFS_012: Profile tagging NPFS_012: profile tagging Jul 7, 2023
@JohnMoehrke JohnMoehrke added the open issue Open Issue mentioned in the Implementation Guide label Oct 24, 2023
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 Open Issue mentioned in the Implementation Guide
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@JohnMoehrke @apinton-Arsenal