Component Content Management Solution

The vendor required to provide component content management solution to manage clinical system content fragmentation and solve challenges in version control, standardization and efficient content management.
- Requirement:
1. Request management: 
•    This is largely managed by an organizational ticketing system (service now), but we are interested in learning of additional options that are available to clinical end-users requesting changes to content through the tool or if this tool can integrate with service now. 
•    The tool, the request should capture, at a minimum the requester, their contact details, a description of the change or request and the ability to include attachments or links.
•    The content type would be required information. 
•    If the solution can integrate with service now, itemizing the information that can flow through to service now would need to be identified. 
•    Any automated routing based on data captured at intake and dashboards available.
2. Authoring content: 
•    Authoring content demands significant effort; implementing standardized templates and robust management features — including creation, versioning, approval, and retirement—can dramatically improve efficiency.
•    The content editor should be structured and component aware, offering rich text capabilities such as formatting, highlighting, font adjustments, tables, embedded images, and spellcheck. 
•    The tool must also enforce required fields, metadata standards, and style or terminology rules, with these validations fully configurable by agency.
•    The solution should support multi-author collaborative editing, including change tracking, version control, and merge review. 
•    It should be easy for users to understand where each item is within the development workflow
•    This stage of authoring, users should also be able to “plug in” pre developed standard components—for example, a standard opioid medication panel or common vital sign fields. 
•    Reuse of components should be maximized to avoid unnecessary duplication.
3. Content management: 
•    The solution will function as the central repository for all content, storing both finalized documents and in-progress drafts. 
•    It must support comprehensive version control for individual components as well as fully assembled documents, including the ability to compare versions (ideally across all historical versions, but at minimum the last one to two), view detailed document comparisons or change tracking, and perform rollbacks when needed.
•    The repository must capture and maintain robust metadata, including editor history, item ids, last edited dates, approval dates, and additional attributes defined by agency. 
•    Metadata schemas must be configurable and enforce required fields at each stage of the content lifecycle.
•    Role based access control is required to ensure appropriate permissions for editing versus view only access. 
•    The solution must also support exportable operational and governance reporting.
4. Component management: 
•    The solution shall provide robust component management capabilities, including support for component libraries with type specific schemas and configurable validation rules. 
•    It must offer real-time “where used” dependency reporting for all components that are referenced, reused, or embedded within other content assets. 
•    The solution shall enable controlled component reuse across all applicable contexts, with the ability to apply full or partial updates to downstream content in an automated yet governed manner. 
•    It shall also support component deprecation workflows, designated replacements, and automated replacement options where appropriate. 
•    The solution must provide comprehensive bulk operation capabilities, including global find and replace across content, batch content updates, batch metadata updates, and batch approval processes.
5. Publishing content: 
•    The content management component of the solution will serve as the primary repository for storing and sharing all materials. 
•    The tool must support multichannel publishing and be able to generate content in multiple formats, including pdf, word, and html. 
•    Agency would like to understand if the solution can be integrated with SharePoint. 
•    The solution would be able to publish content both within the source tool and directly to a designated location in our organization’s SharePoint environment.