> For the complete documentation index, see [llms.txt](https://contacttracingplaybook.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://contacttracingplaybook.org/how-to-do-contact-tracing/data-management-systems.md). # Data management ## Principles of data management 1. Make collected data accessible: The format of a positive laboratory test result for COVID-19, as well as the necessary associated patient information, should be accessible to both clinical and public health entities in either “near real time” or in aggregate as necessary. Ideally patient data is ultimately shared with the patient’s provider. 2. Import relevant available health data: A system capable of automatically importing relevant prior contact, demographic, and clinical records would substantially reduce the burden on the contact tracing and medical workforce. Regulatory barriers to accessing this information (e.g., HIPAA Minimum Necessary restriction) can be overcome with a [statement from the federal HHS Office of Civil Rights](https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/minimum-necessary-requirement/index.html) or an assertion from the State. 3. Make data usable: Investing in the above principles to aggregate and access relevant health information will be wasted if contact tracers and other public health employees aren’t clear on how to access it and then share relevant recommendations with cases and contacts. Ideally, programs have easy-to-use user interfaces for data review and entry, but, alternatively, detailed visual training programs can ensure the workforce is taking advantage of useful data. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://contacttracingplaybook.org/how-to-do-contact-tracing/data-management-systems.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.