How to Assemble
In pulling together Patient-Centered Core Impact Sets (PC-CIS) itself, the previously discussed concepts of transparency and inclusivity should be followed in the final compilation.
The report of impacts should include (but need not be limited to):
The impact information itself should be presented in a logical format (for example, as outlined in this reporting tool), explaining how impacts were filtered or narrowed at each stage. The report should include at least:
The same need for transparency described earlier in the Blueprint is relevant in the compilation of the final report.
Additional Considerations for Assembling and Reporting
Including Other Information
If possible and where relevant, the report may include things that are related to the core, but are not core impacts, such as tools or measures identified for relevant impact concepts – but only if they have been assessed by the PC-CIS developers as specifically addressing impacts in the PC-CIS and are assessed for patient centricity, sound methods, and a relevant context(s) of use. Assessing these tools can be challenging and resource intensive. In essence, before you recommend a tool, you as the PC-CIS developer, need to be comfortable that the tool is measuring what it claims to measure and is a useful extension of the PC-CIS in application. These add-ons are not core impacts but can help with efficiency in application of the core set. They are not required for a PC-CIS.
Dissemination and Open-Source Sharing of PC-CIS
In the spirit of accessibility and mutual opportunities to learn, it is best practice to make PC-CIS available in a variety of locations that are accessible and usable by patients and other stakeholders. It would also be valuable to disseminate PC-CIS through non-traditional channels, such as patient advocacy organization websites and other patient-facing media and online channels.
Arthritis Use Case