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

Synthea Team Updates for BFD-458 (Test with Synthea Data) #775

Conversation

hadleynet
Copy link
Contributor

Change Details

This PR updates the BFD-458-test-synthea-data-2 branch to account for all the RIF files that the Synthea bb-export branch outputs.

In order for these changes to function, the environment needs to have a set a SYNTHEA_OUTPUT_DIR environment variable that points to the Synthea RIF files. If Synthea is configured to export RIF, these files will be in {path}/synthea/output/bfd, but your testing environment could also have a static synthetic dataset stashed somewhere (or none at all), hence the environment variable.

Acceptance Validation

Given a set of synthetic RIF files, do the integration tests successfully pass for the bfd-pipeline-rif-load and bfd-server-war projects?

Feedback Requested

Changes to make, if necessary.

External References

Security Implications

The synthetic data generated by Synthea contains no privacy or security concerns or restrictions.

  • new software dependencies

    • Optional use of Synthea to generate RIF files.
  • altered security controls

    • N/A
  • new data stored or transmitted

    • Optional use of Synthea generated synthetic RIF files. These files have no privacy or security restrictions.
  • security checklist is completed for this change

  • requires more information or team discussion to evaluate security implications

@christrotteradhoc christrotteradhoc marked this pull request as draft February 2, 2022 16:02
@christrotteradhoc
Copy link
Contributor

Closing since this already merged from another branch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants