As @Kadir mentioned, from a technical standpoint, you can link issues in Jira to Confluence pages but you may not need that.
@rosemadder I've prepared this article some time ago precisely on the topic of compliance in regulated environments.
In Xray you have full traceability, from epic > stories > tests > runs > defects.
But this traceability is not static; actually, it's multidimensional. In other words, in Xray the traceability is calculated depending on the version/environment/scope you aim to analyze. For example, traceability and related coverage for v1 of the product can be completly different from the one obtained for v2 of the product (e.g., due to different code, different bugs, different test results)
Your code commits can be linked to any jira issue, including epics, stories, and even Tests (which are Jira issues), in case you're implementing the related test automation code.
You can also generate a report, manually or automatically, with your testing specification, planning, results (please see the article for more info).
Hope that helps