Refactor/redesign recommendation pages

[c-schuler]

• Add a Table of Contents (TOC) right under the Recommendation reference/statement that links to each topic on the page.
• Add an “Overview” section right under the Recommendation reference/statement
  • Should mention that the recommendation may be represented in multiple variations where each variation corresponds to the CDS Hook by which it was meant to be triggered/evaluated.
• Add tabs as the method for showing multiple variations on the same page - a tab for each variation.
• Functional Descriptions and diagrams should be hook/variation-specific
• The diagrams can be kept as images, but could use some attention with respect to right-sizing them throughout.
• Add a short introduction to the “data elements” table (the blue table)
• The data elements table (blue table) should be converted to an HTML representation rather than an image so that we can do linking from the expressions contained in the table to the effective data requirements and CQL. We’re free to take some liberties with it rather than being constrained to using exactly what Floyd provides.
• Add an “Effective Data Requirements” section below the functional description’s data elements table (the blue table with the expressions).
  • Add the “Effective Data Requirements” to the PlanDefinition processing and to the refresh/publish tooling - same as what was done for Measure.
  • Add a link below the blue definitions table to the effective data requirements section of the generated PlanDefinition narrative from the recommendation page.
  • Would include the fhirQueryPatterns generated
• The “Common Libraries” partial should be embedded in the recommendation’s ‘Content’ section rather than just a link to it. Ideally, all libraries that are used in the recommendation implementation should be listed right on the page directly.
• The “Common Libraries” partial needs to be updated to ensure that it includes the full list of common libraries (e.g., OpioidCDSRoutines is missing).