METHODS: The content development team is using an Agile approach to the project. Conditions were grouped by category and assigned a priority based on urgency, volume of reporting, and input from partner jurisdictions. Using the logic from the CSTE position statements, the content development team drafted proposed criteria along with the appropriate value sets and wrote the clinical rules statements used for the clinical decision support engine. Each week, by condition category and prioritization groups, conditions were presented to the CSTE Content Vetting Workgroup for subject-matter verification and input. Input was considered and incorporated into a final revision of the content.
RESULTS: The content development team has developed content for several conditions based upon the priority categorization. Several of these conditions have been reviewed through the Content Vetting Workgroup and input has been carefully considered and incorporated. This presentation will highlight some of the common themes discussed in the content development process, using HIV and hepatitis as examples. These themes include: the challenge of moving some requirements to machine-processable language; the ability to accurately capture the current state of reporting, and the potential for jurisdictions to adopt or adapt the developed content.
CONCLUSIONS: Moving to electronic case reporting has required consideration of how to automate a process that was designed for and conducted by humans. Through the current phase of RCKMS development, machine-processable information that can meet the reporting needs of states and local jurisdictions has been developed for several nationally notifiable conditions with the expertise of content and language experts. At the end of this phase of the RCKMS project, we aim to have standardized, machine-processable reporting criteria for all nationally notifiable conditions which have been fully vetted with domain experts from each category of conditions.