-
Notifications
You must be signed in to change notification settings - Fork 0
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
Is having a contact person in the manifest essential? #51
Comments
P.S. I do consider this a pretty minor issue. Just something that seemed odd to me. |
In terms of a proposed approach, I was thinking it might make sense to have the contact information for a health center be identified when the health center is registering for a client ID to use for the submission. |
Need to discuss with BPHC SMEs, this requirement was levied to mimic the existing EHB approach where there is a contact person that interacts with HRSA when there are issues with the submissions and reporting. |
The UDS+ Project is collecting PII. The goal is to mitigate collection of PHI based on HHS Safe Harbor. |
HRSA collects PII for operational purposes but still mandates conformance to the De-identification requirements as per HHS provisions as specified in the IG. So the Contact Name for the Health Center falls under the operations requirement and will be retained in the manifest. |
In https://fhir.org/guides/hrsa/uds-plus/StructureDefinition-uds-plus-import-manifest.html
Is the inclusion of the hcContactPerson in the manifest with a required given and family name necessary? The proposed approach has a few side effects:
The text was updated successfully, but these errors were encountered: