-
-
Notifications
You must be signed in to change notification settings - Fork 29
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
Export Consent Forms (Markdown) #40
Conversation
@PSchmiedmayer PR ready for review, keep in mind that the |
@PSchmiedmayer Seems like the pipeline is running into some issues:
|
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #40 +/- ##
==========================================
- Coverage 82.03% 81.79% -0.23%
==========================================
Files 32 32
Lines 840 873 +33
==========================================
+ Hits 689 714 +25
- Misses 151 159 +8
... and 1 file with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
@philippzagar Thank you for the PR. I will give StanfordSpezi/SpeziOnboarding#26 a review and then we can merge this one here. Also took a look at the build errors in #39 & #41, that should also fix the CI in this PR 👍 |
…feat/export-consent-forms
@PSchmiedmayer Ready for review after you reviewed StanfordSpezi/SpeziOnboarding#26 :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the great additions, looking forward to see this PR being merged!
I had a small comment regarding the functionality to upload the consent document to Firebase Cloud Storage. Apart from this the PR looks great and the code is well structured 🚀
Note to ourselves: We need to merge StanfordSpezi/SpeziFirebase#17 first and adjust the dependencies within this branch |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, thank you for the changes; looks great and happy to merge it once we have the related PRs merged and ready 👍
TemplateApplication.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolved
Outdated
Show resolved
Hide resolved
TemplateApplication.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolved
Outdated
Show resolved
Hide resolved
Nice, great job @philippzagar! 🚀 |
<!-- This source file is part of the Stanford Spezi open-source project SPDX-FileCopyrightText: 2022 Stanford University and the project authors (see CONTRIBUTORS.md) SPDX-License-Identifier: MIT --> Until now, users could view and sign a consent document in the Spezi template application using the `SpeziOnboarding` package. However, the app did not offer any provision to save or export the signed consent document. In the medical domain, the consent form collection is especially important in order to serve as legal cover. See StanfordSpezi/SpeziOnboarding#7. Utilizes: StanfordSpezi/SpeziFirebase#17 - The template application now utilizes the `OnboardingConsentView` of `SpeziOnboarding`, providing an export and share functionality of the signed consent form as a PDF. Incorporated where necessary. Associated with StanfordSpezi/SpeziOnboarding#26 -- By submitting creating this pull request, you agree to follow our [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md): - [X] I agree to follow the [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md). --------- Co-authored-by: Paul Schmiedmayer <PSchmiedmayer@users.noreply.github.com>
<!-- This source file is part of the Stanford Spezi open-source project SPDX-FileCopyrightText: 2022 Stanford University and the project authors (see CONTRIBUTORS.md) SPDX-License-Identifier: MIT --> # *Export Consent Forms (Markdown)* ## ♻️ Current situation & Problem Until now, users could view and sign a consent document in the Spezi template application using the `SpeziOnboarding` package. However, the app did not offer any provision to save or export the signed consent document. In the medical domain, the consent form collection is especially important in order to serve as legal cover. See StanfordSpezi/SpeziOnboarding#7. Utilizes: StanfordSpezi/SpeziFirebase#17 ## ⚙️ Release Notes - The template application now utilizes the `OnboardingConsentView` of `SpeziOnboarding`, providing an export and share functionality of the signed consent form as a PDF. ## 📚 Documentation Incorporated where necessary. Associated with StanfordSpezi/SpeziOnboarding#26 ## ✅ Testing -- ## 📝 Code of Conduct & Contributing Guidelines By submitting creating this pull request, you agree to follow our [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md): - [X] I agree to follow the [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md). --------- Co-authored-by: Paul Schmiedmayer <PSchmiedmayer@users.noreply.github.com>
<!-- This source file is part of the Stanford Spezi open-source project SPDX-FileCopyrightText: 2022 Stanford University and the project authors (see CONTRIBUTORS.md) SPDX-License-Identifier: MIT --> # *Export Consent Forms (Markdown)* ## ♻️ Current situation & Problem Until now, users could view and sign a consent document in the Spezi template application using the `SpeziOnboarding` package. However, the app did not offer any provision to save or export the signed consent document. In the medical domain, the consent form collection is especially important in order to serve as legal cover. See StanfordSpezi/SpeziOnboarding#7. Utilizes: StanfordSpezi/SpeziFirebase#17 ## ⚙️ Release Notes - The template application now utilizes the `OnboardingConsentView` of `SpeziOnboarding`, providing an export and share functionality of the signed consent form as a PDF. ## 📚 Documentation Incorporated where necessary. Associated with StanfordSpezi/SpeziOnboarding#26 ## ✅ Testing -- ## 📝 Code of Conduct & Contributing Guidelines By submitting creating this pull request, you agree to follow our [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md): - [X] I agree to follow the [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md). --------- Co-authored-by: Paul Schmiedmayer <PSchmiedmayer@users.noreply.github.com>
<!-- This source file is part of the Stanford Spezi open-source project SPDX-FileCopyrightText: 2022 Stanford University and the project authors (see CONTRIBUTORS.md) SPDX-License-Identifier: MIT --> # *Export Consent Forms (Markdown)* ## ♻️ Current situation & Problem Until now, users could view and sign a consent document in the Spezi template application using the `SpeziOnboarding` package. However, the app did not offer any provision to save or export the signed consent document. In the medical domain, the consent form collection is especially important in order to serve as legal cover. See StanfordSpezi/SpeziOnboarding#7. Utilizes: StanfordSpezi/SpeziFirebase#17 ## ⚙️ Release Notes - The template application now utilizes the `OnboardingConsentView` of `SpeziOnboarding`, providing an export and share functionality of the signed consent form as a PDF. ## 📚 Documentation Incorporated where necessary. Associated with StanfordSpezi/SpeziOnboarding#26 ## ✅ Testing -- ## 📝 Code of Conduct & Contributing Guidelines By submitting creating this pull request, you agree to follow our [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md): - [X] I agree to follow the [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md). --------- Co-authored-by: Paul Schmiedmayer <PSchmiedmayer@users.noreply.github.com>
<!-- This source file is part of the Stanford Spezi open-source project SPDX-FileCopyrightText: 2022 Stanford University and the project authors (see CONTRIBUTORS.md) SPDX-License-Identifier: MIT --> Until now, users could view and sign a consent document in the Spezi template application using the `SpeziOnboarding` package. However, the app did not offer any provision to save or export the signed consent document. In the medical domain, the consent form collection is especially important in order to serve as legal cover. See StanfordSpezi/SpeziOnboarding#7. Utilizes: StanfordSpezi/SpeziFirebase#17 - The template application now utilizes the `OnboardingConsentView` of `SpeziOnboarding`, providing an export and share functionality of the signed consent form as a PDF. Incorporated where necessary. Associated with StanfordSpezi/SpeziOnboarding#26 -- By submitting creating this pull request, you agree to follow our [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md): - [X] I agree to follow the [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md). --------- Co-authored-by: Paul Schmiedmayer <PSchmiedmayer@users.noreply.github.com>
<!-- This source file is part of the Stanford Spezi open-source project SPDX-FileCopyrightText: 2022 Stanford University and the project authors (see CONTRIBUTORS.md) SPDX-License-Identifier: MIT --> Until now, users could view and sign a consent document in the Spezi template application using the `SpeziOnboarding` package. However, the app did not offer any provision to save or export the signed consent document. In the medical domain, the consent form collection is especially important in order to serve as legal cover. See StanfordSpezi/SpeziOnboarding#7. Utilizes: StanfordSpezi/SpeziFirebase#17 - The template application now utilizes the `OnboardingConsentView` of `SpeziOnboarding`, providing an export and share functionality of the signed consent form as a PDF. Incorporated where necessary. Associated with StanfordSpezi/SpeziOnboarding#26 -- By submitting creating this pull request, you agree to follow our [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md): - [X] I agree to follow the [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md). --------- Co-authored-by: Paul Schmiedmayer <PSchmiedmayer@users.noreply.github.com>
Export Consent Forms (Markdown)
♻️ Current situation & Problem
Until now, users could view and sign a consent document in the Spezi template application using the
SpeziOnboarding
package. However, the app did not offer any provision to save or export the signed consent document.In the medical domain, the consent form collection is especially important in order to serve as legal cover.
See StanfordSpezi/SpeziOnboarding#7.
Utilizes: StanfordSpezi/SpeziFirebase#17
⚙️ Release Notes
OnboardingConsentView
ofSpeziOnboarding
, providing an export and share functionality of the signed consent form as a PDF.📚 Documentation
Incorporated where necessary.
Associated with StanfordSpezi/SpeziOnboarding#26
✅ Testing
--
📝 Code of Conduct & Contributing Guidelines
By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines: