You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears that there's redundancy in mapping the same information on DocumentReference when it could instead be captured within Attachment. Is it necessary to impose this restriction? Alternatively, could we rephrase it to specify that if the information isn't available in Attachment, it can be accessed through this standard extension?
The text was updated successfully, but these errors were encountered:
teslajoy
changed the title
General Feedback - [Short Description of Feedback]
General Feedback - duplicate efforts of mapping on File/DocumentReference
Nov 11, 2024
teslajoy
changed the title
General Feedback - duplicate efforts of mapping on File/DocumentReference
For Comment Feedback for: duplicate efforts of mapping on File/DocumentReference
Nov 14, 2024
What were you reviewing?
https://nih-ncpi.github.io/ncpi-fhir-ig-2/StructureDefinition-ncpi-file.html
Suggested Improvements:
It appears that there's redundancy in mapping the same information on DocumentReference when it could instead be captured within Attachment. Is it necessary to impose this restriction? Alternatively, could we rephrase it to specify that if the information isn't available in Attachment, it can be accessed through this standard extension?
The text was updated successfully, but these errors were encountered: