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.

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

Time synchronization requirements #202

Closed
AnnaFeiler opened this issue Jul 24, 2023 · 2 comments · Fixed by #212
Closed

Time synchronization requirements #202

AnnaFeiler opened this issue Jul 24, 2023 · 2 comments · Fixed by #212
Assignees
Labels
NTP Issue related to Network Time Protocol SES Safety, Effectiveness, Security related issue

Comments

@AnnaFeiler
Copy link
Collaborator

During the workshop, we found that we are missing the following requirements:

  • Add a requirement, that the responsible organization needs to configure their devices that are intended to execute system functions together in a way, that they all synchronize to the same ntp server.
  • Add a requirement, that beeing conneted to an ntp server is a precondition for starting to execute system functions. Otherwise, we cannot say anything about certificate validity.
@AnnaFeiler AnnaFeiler added NTP Issue related to Network Time Protocol Comment NEW A submitted comment waiting to be reviewed and dispositioned SES Safety, Effectiveness, Security related issue labels Jul 24, 2023
@AnnaFeiler AnnaFeiler added this to the SDPi 1.2 Review milestone Jul 24, 2023
@ToddCooper ToddCooper removed the Comment NEW A submitted comment waiting to be reviewed and dispositioned label Jul 28, 2023
@ToddCooper
Copy link
Collaborator

@AnnaFeiler : What is the difference between this issue and the general NTP topic coming out of the workshop?

@AnnaFeiler
Copy link
Collaborator Author

This one captures two concrete requirements that we already agreed upon during the workshop while the other tickets take care of bigger open topics and follow up actions.

@AnnaFeiler AnnaFeiler linked a pull request Aug 16, 2023 that will close this issue
2 tasks
d-gregorczyk added a commit that referenced this issue Dec 1, 2023
* Added private coding system identifier definition in volume 3, updated private mdc code mapping in volume 2 gateways.

* 179 how is an advisory modelled contradictory definitions in a pkp and ihe acm (#232)

* Detailded mapping requirements for advisories.

* Detailded mapping requirements for advisories.

* #233 removed comment

* #233 Add changelog entry.

* 24 sexgender mapping is incorrect (#229)

* Added requirements regarding patient's sex mapping and added mapping of sex to a OBX.

* Reworked the PID-8 Sex mapping.

* Corrected reference

* Reworded requirement R8107; added new requirement R8122

* 235 explicit sdpi scope statement (#239)

* Initial language for an SDPi Scope

Crafted initial language (bullets) toward an SDPi Scope statement,.

* SDPi Scope Update

Updated both draft scope language as well as the organization of the sections.

* Finalized Scope Language

After SDPi Friday review 3 November.

* Updated changelog.md for Scope of Application

#235

* Updated Title Page with additional HL7 focused content (#242)

* Updated Title Page with additional HL7 focused content

Added HL7 recognition + PDF language + STU/TI vs. use it in products now!

* Swapped Logo Order

HL7 before IHE

* Update asciidoc/volume3/tf3-ch-8.3.2-biceps-content.adoc

Co-authored-by: David Gregorczyk <54440227+d-gregorczyk@users.noreply.github.com>

* Update asciidoc/volume3/tf3-ch-8.3.2-biceps-content.adoc

Co-authored-by: David Gregorczyk <54440227+d-gregorczyk@users.noreply.github.com>

* Update asciidoc/volume3/tf3-ch-8.3.2-biceps-content.adoc

Co-authored-by: David Gregorczyk <54440227+d-gregorczyk@users.noreply.github.com>

* Proposed changes to glossary table to address issue #166 (#241)

* Update asciidoc/volume3/tf3-ch-8.3.2-biceps-content.adoc

Co-authored-by: David Gregorczyk <54440227+d-gregorczyk@users.noreply.github.com>

* Added clarifying note to reformulated requirement R0702

* #202 added two new time sync requirement from the workshop (#212)

* Update asciidoc/volume3/tf3-ch-8.3.2-biceps-content.adoc

* ChangeLog updates for #57 (and also #166)

* Added private coding system identifier definition in volume 3, updated private mdc code mapping in volume 2 gateways.

* Update asciidoc/volume3/tf3-ch-8.3.2-biceps-content.adoc

Co-authored-by: David Gregorczyk <54440227+d-gregorczyk@users.noreply.github.com>

* Update asciidoc/volume3/tf3-ch-8.3.2-biceps-content.adoc

Co-authored-by: David Gregorczyk <54440227+d-gregorczyk@users.noreply.github.com>

* Update asciidoc/volume3/tf3-ch-8.3.2-biceps-content.adoc

Co-authored-by: David Gregorczyk <54440227+d-gregorczyk@users.noreply.github.com>

* Update asciidoc/volume3/tf3-ch-8.3.2-biceps-content.adoc

Co-authored-by: David Gregorczyk <54440227+d-gregorczyk@users.noreply.github.com>

* Added clarifying note to reformulated requirement R0702

* Update asciidoc/volume3/tf3-ch-8.3.2-biceps-content.adoc

* ChangeLog updates for #57 (and also #166)

* ChangeLog updates for #57 (and also #166) - hopefully without conflicts now

* ChangeLog updates for #57 (and also #166) - hopefully without conflicts now

* #57 Revert changelog to master

* #57 Add changelog entries.

* #57 Boyscout changelog

* #57 Move changelog entries from 1.1.0 to unreleased section

---------

Co-authored-by: riechkathrin <kathrinpia.riech@draeger.com>
Co-authored-by: David Gregorczyk <david.gregorczyk@web.de>
Co-authored-by: Todd "AFC!" Cooper <ToddCooperAFC@gmail.com>
Co-authored-by: David Gregorczyk <54440227+d-gregorczyk@users.noreply.github.com>
Co-authored-by: Javier Espina <47562907+JavierEspina@users.noreply.github.com>
Co-authored-by: JavierEspina <javier.espina@philips.com>
Co-authored-by: AnnaFeiler <113893906+AnnaFeiler@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NTP Issue related to Network Time Protocol SES Safety, Effectiveness, Security related issue
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants