SES Non-Comprehensive Note Added (#351)

* SES Non-Comprehensive Note Added

A note was added to section 1:2.2 to indicate that the SES sections in the document are not intended to represent comprehensive risk management requirements and that implementers must ensure that appropriate RM processes have been completed.

* Simple formatting update

Highlighted the primary point of the HL7 ballot comment.

CHANGELOG.md

@@ -19,6 +19,7 @@ Each section shall contain a list of action items of the following format: `<bri
 - Fixed action URN in waveform stream example ([#292](https://github.com/IHE/DEV.SDPi/issues/292))
 - Clarified intentionality of difference between ad-hoc and managed discovery ([#317](https://github.com/IHE/DEV.SDPi/issues/317))
 - Clarified FHIR Gateway support for multiple paradigms ([#264](https://github.com/IHE/DEV.SDPi/issues/264))
+- Clarified that the SES sections are not comprehensive for risk management ([#271](https://github.com/IHE/DEV.SDPi/issues/271))
 
 ### Editorial Fixes
 - Added deprecation notice for three requirements due to expected impact of BICEPS standard corrigendum ([#334](https://github.com/IHE/DEV.SDPi/issues/334))

asciidoc/volume1/tf1-ch-2-overview.adoc

@@ -32,6 +32,9 @@ Thus the "Safety, Effectiveness and Security - Requirements and Considerations"
 Note that specific requirements from the above mentioned standards, may also be captured in <<vol1_appendix_b_referenced_standards_conformance>>.
 Generally, requirements from these standards would be mapped to the appropriate "Safety, Effectiveness and Security - Requirements and Considerations" sections throughout the specification.
 
+NOTE:  The *_SES sections in this document are not intended to be comprehensive_*, but provide helpful guidance to risk managers.
+Implementers must ensure that all appropriate risk management processes have been performed.
+
 // 2.3
 [#vol1_clause_integration_profiles_overview]
 === Integration Profiles Overview