Stream: patient empowerment
Topic: Task.businessStatus
Abbie Watson (Dec 16 2020 at 15:19):
Hello,
Based on my experiences to date building one of these Task servers, I would like to submit the following CodeSystem for consideration for Task.businessStatus.
The CodeSystem below is based off of IETF RFC2616 and IETF RFC 7231, with custom 6xx codes from 45 CFR §164.526 (a)(1). This approach allows automated mapping to existing API endpoints which the Task resource may overlap with, while also allowing for file room clerks and clinicians to update records manually. It also provides a great deal of specificity of error edge cases which the HIPAA/GDPR workflows are likely to encounter, regardless of which FHIR resource or URI endpoint is being used.
I am providing the CodeSystem via JSON and Word document, and will be uploading it to the reference server next week unless anybody else has an alternative proposal.
CodeSystem.hipaa-http-business-status-mapping.json
Proposed-CodeSystem-for-HIPAA-GDPR-Correction-Requests.docx
Proposed-CodeSystem-for-HIPAA-GDPR-Correction-Requests.png
John Keyes (Dec 16 2020 at 15:33):
(deleted)
Last updated: Apr 12 2022 at 19:14 UTC
