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

Export Consent Forms (Markdown) #40

Merged
merged 29 commits into from
Oct 16, 2023
Merged

Conversation

philippzagar
Copy link
Member

@philippzagar philippzagar commented Oct 3, 2023

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 and Contributing Guidelines:

@philippzagar
Copy link
Member Author

@PSchmiedmayer PR ready for review, keep in mind that the feat/export-consent-forms branch of SpeziOnboarding is currently set as a dependency so that you are able to test locally / Pipeline succeeds. As soon as StanfordSpezi/SpeziOnboarding#26 is merged and tagged, I'll update the dependency to a tagged version.

@philippzagar
Copy link
Member Author

@PSchmiedmayer Seems like the pipeline is running into some issues:

Error: Encountered a fatal error while running "/Users/runner/hostedtoolcache/CodeQL/2.14.6/x64/codeql/codeql database finalize --finalize-dataset --threads=4 --ram=13004
/Users/runner/work/SpeziTemplateApplication/SpeziTemplateApplication/.codeql/swift". 
Exit code was 32 and error was: CodeQL detected code written in Swift but could not process any of it. Review our troubleshooting guide at https://gh.io/troubleshooting-code-scanning/no-source-code-seen-during-build.

@codecov
Copy link

codecov bot commented Oct 3, 2023

Codecov Report

Merging #40 (adf0e97) into main (692c7c9) will decrease coverage by 0.23%.
The diff coverage is 84.79%.

Additional details and impacted files

Impacted file tree graph

@@            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     
Files Coverage Δ
TemplateApplication/Onboarding/Consent.swift 94.12% <100.00%> (-1.53%) ⬇️
...emplateApplication/Onboarding/OnboardingFlow.swift 97.23% <100.00%> (ø)
TemplateApplication/Onboarding/Welcome.swift 100.00% <100.00%> (ø)
TemplateApplication/TemplateAppDelegate.swift 97.83% <100.00%> (+0.10%) ⬆️
...n/Onboarding/OnboardingFlow+PreviewSimulator.swift 0.00% <0.00%> (ø)
...plateApplication/TemplateApplicationStandard.swift 51.24% <83.34%> (+13.60%) ⬆️

... and 1 file with indirect coverage changes


Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 692c7c9...adf0e97. Read the comment docs.

@PSchmiedmayer
Copy link
Member

@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 👍

@PSchmiedmayer PSchmiedmayer added the enhancement New feature or request label Oct 4, 2023
@philippzagar
Copy link
Member Author

@PSchmiedmayer Ready for review after you reviewed StanfordSpezi/SpeziOnboarding#26 :)

Copy link
Member

@PSchmiedmayer PSchmiedmayer left a 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 🚀

TemplateApplication/TemplateApplicationStandard.swift Outdated Show resolved Hide resolved
@philippzagar
Copy link
Member Author

Note to ourselves: We need to merge StanfordSpezi/SpeziFirebase#17 first and adjust the dependencies within this branch

Copy link
Member

@PSchmiedmayer PSchmiedmayer left a 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 👍

@philippzagar philippzagar enabled auto-merge (squash) October 16, 2023 06:16
@philippzagar philippzagar merged commit 5f4e95c into main Oct 16, 2023
6 checks passed
@philippzagar philippzagar deleted the feat/export-consent-forms branch October 16, 2023 06:43
@PSchmiedmayer
Copy link
Member

Nice, great job @philippzagar! 🚀

NikolaiMadlener pushed a commit to NikolaiMadlener/SpeziTemplateApplication that referenced this pull request Oct 18, 2023
<!--

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>
NikolaiMadlener pushed a commit to NikolaiMadlener/SpeziTemplateApplication that referenced this pull request Oct 18, 2023
<!--

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>
NikolaiMadlener pushed a commit to NikolaiMadlener/SpeziTemplateApplication that referenced this pull request Oct 18, 2023
<!--

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>
NikolaiMadlener pushed a commit to NikolaiMadlener/SpeziTemplateApplication that referenced this pull request Oct 18, 2023
<!--

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>
NikolaiMadlener pushed a commit to NikolaiMadlener/SpeziTemplateApplication that referenced this pull request Oct 18, 2023
<!--

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>
NikolaiMadlener pushed a commit to NikolaiMadlener/SpeziTemplateApplication that referenced this pull request Oct 18, 2023
<!--

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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

2 participants