Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SES Non-Comprehensive Note Added #351

Merged
merged 2 commits into from
Dec 9, 2024
Merged

SES Non-Comprehensive Note Added #351

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
192b9b9
SES Non-Comprehensive Note Added
ToddCooper Dec 6, 2024
d18a663
Simple formatting update
ToddCooper Dec 6, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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))
Expand Down
3 changes: 3 additions & 0 deletions asciidoc/volume1/tf1-ch-2-overview.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
Loading