STARS Implementation Guide - Local Development build (v0.3.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

Migration Guide

Migration Guide

Existing systems will need to migrate from the old legacy STARS Engine to the new Stars.Client to continue to make submissions in the future (no timeline has been set to remove the old systems as yet). This will involve laboratories completing a number of tasks on their own systems and procedures including such as:

• Pre-install meeting with lab outlining settings and processes required from internal IT, timelines from both parties, etc.
• Reveiew new field lists and descriptions. See Profile-ServiceRequest and Profile-DiagnosticReport.
• Modify internal LIMS processes to export updated field lists. See Mapping ServiceRequest from Legacy JobSend and Mapping DiagnosticReport from Legacy ResultSend.
• Modify internal LIMS processes to export the new locations. See Folders and Paths.
• Install and configure new Stars.Client (Both clients should be able to be run side-by-side initially so jobs can be selectively tested using the new infrastructure). See Stars Client.
• Ensure terminologies are accurate. The legacy lists (known as ValueSets) and mappings (knows as ConceptMaps) will continue to be utilised. A new process to update these mappings will be released shortly.

Testing Plan

Testing the new process with a testing plan similar to below will ensure a smooth transitio over to the new system.

• export job/samples to be sent to acdp01 for testing
• save csv into 'outgoing' folder
  • check all required fields are entered as expected
  • check any optional fields are entered as expected
• verify message has been sent to acdp01
• advise acdp01 that test messages have been sent

• acdp01 will received sent correctly to acdp01

• acdp01 will accession the received samples and assign results
• acdp01 will send results back to users lab
  • verify message has been received
• message will get converted to csv in the 'incoming' folder
  • check all results are received as expected

• (optional) import results into your LIMS

• move into production
• disable old system when ready