SF - Enrollments Flat File - Outbound
The SF - Enrollments Flat File - Outbound is a standard flow that provides the baseline functionality for creation of an enrollment file from existing data to be sent to a party, and also provides the ability to customize values for integration-specific settings. The flow should be both customer and file-type agnostic, and be used by integration builders as a starting point for any integration that is built. It should also standardize the way a flow behaves, as well as log messages and status setting, to help with standardizing the way we build integrations for our customers.
Flow Logic
Configuration of the Flow Widgets
While configuring the widgets composing this standard flow, only the following parameters should be set by the user:
Widget (s) | Parameter |
|---|---|
CRON_EXPRESSION | Trigger CRON |
NETWORKID | Translate from FHIR to JSON Merge - Flat File Generation |
FILE_DEFINITION_ID | Translate from FHIR to JSON Merge - Flat File Generation |
FILE_DEFINITION_VERSION | Translate from FHIR to JSON Merge - Flat File Generation |
COMPONENT_UNIQUE_ID_1 | Flat Output File |
SFTP_CONNECTION_ID | Flat Output File |
NETWORK | Flat Output File |
ENV | Flat Output File |
OUTCOMING_FILENAME_SHOVEL | Flat Output File |
Trigger CRON
trigger-schedule: CRON_EXPRESSION. (E.g.: */10 * * * * 0 0 15 ? * MON-FRI)
For more information on how to configure this shovel operation, view Trigger.
Search Enrollment Records
This shovel operation sets a fixed output collection to primary.
For more information on how to configure this shovel operation, view Search FHIR Enrollements.
Translate from FHIR to JSON
Tip
Use following Schema Definition: Section : “Create Enrollment Inbound Flat File Schema”
For more information on how to configure this shovel operation, view Translate From FHIR.
Standard Date Formats Transformation
Tip
The Date should adhere to the following format: YYMMDD
For more information on how to configure this shovel operation, view Remap Document.
Sanitize Document
This shovel operation leaves the transformed data in a document to be picked up for the MergeAndTranslateToFile.
For more information on how to configure this shovel operation, view Remap Document.
Merge - Flat File Generation
For more information on how to configure this shovel operation, view Merge and Translate to File.
Unmerged Branch
Enrolments Flat File - Unmerge txn Sets
For more information on how to configure this shovel operation, view Commit Transaction.
End Branch
Flat Output File
This Shovel Operation stores the file into the FTP server.
id: COMPONENT_UNIQUE_ID_1 that is a user-defined unique identifier and must be unique across all integrations.
connectionId: FTP_CONNECTION_ID, where the FTP connection ID is the one that was defined during the implementation.
directory: /NETWORK/ENV/out, which is the path to the destination folder in the FTP server. NETWORK is the receiver's name and ENV is the environment or lifecycle's stage name for this implementation.
For more information on how to configure this shovel operation, view Commit Transaction.
Enrollments Flat File - Outbound END
For more information on how to configure this shovel operation, view Commit Transaction.