You can implement this in a Health Connect Cloud interoperability production, but the returned material does not give enough detail to fully prescribe whether you should use a scheduled business service or Task Manager for your exact nightly file-generation logic. What is clearly supported is:
- You can create and manage an interoperability production in Health Connect Cloud through the Management Portal. [1]
- For writing HL7 content to files,
EnsLib.HL7.Operation.FileOperationis specifically identified as the class whose purpose is to create a file in a directory and add HL7 messages to it. [1][2] - In Health Connect Cloud, the documented cloud-oriented file workflow is to use productions with business services, business processes, and business operations, and use SFTP integration with folders in your tenant’s S3 bucket rather than relying on a traditional local server workflow. [3]
- If timing matters, the deployment time zone can be configured, and the default is UTC, so that is relevant for a nightly time such as 11:45 PM. [1]
For your scenario, the best-supported approach from the returned documents is:
- Create a production in Health Connect Cloud. [1][3]
- Use a business operation for file output; the returned material specifically points to
EnsLib.HL7.Operation.FileOperationfor creating a file and adding HL7 messages to it. [1][2] - If this needs to be cloud-based rather than written to a deployment-local directory, use the documented SFTP/S3 pattern for output files. [3]
- Set the deployment time zone correctly so the nightly schedule aligns with your intended local time. [1]
If your design is closer to “create placeholder files first, then append live HL7 messages later,” the retrieved material does support the file-append concept through EnsLib.HL7.Operation.FileOperation, but it does not provide the exact implementation steps for generating 17 files with names like xxx__YYYYMMDD.txt, using the next day’s date, and writing "Dummy Word" before later appending live data. [1][2]
On scheduling:
- One returned source shows that productions have a Schedule feature for business services, and that this can be used to run within configured start/stop times. [4][5]
- Another returned source shows that custom scheduled tasks can be built by extending
%SYS.Task.Definitionand implementingOnTask(). [6]
However, the retrieved material does not explicitly say which of those two is the recommended pattern in Health Connect Cloud for your exact use case, nor does it provide the ObjectScript/VS Code implementation needed for your filename/date/content requirements. [1][4][6]
Note: Do not confuse the tenant-level Files page with deployment-level Files pages. The tenant-level Files page lets you set up the SFTP feature for all of the deployments on your tenant. The deployment-level Files pages let you upload files from your local computer to a deployment. [1][3]
Note: Some of the functionality described in this section may not be available to all users, depending on their role on the development team. For more information, see Tenants Page. [1]
So, from the available material, the safest answer is: use a Health Connect Cloud production and a file-writing business operation, and for cloud storage use the documented SFTP/S3-based workflow rather than assuming a writable local server area. The exact “scheduled nightly creation of 17 seed files with next-day names and hardcoded content” implementation is not described in the returned documents. [1][3][2]
Sources:
- Log in to post comments