This feature is essential to streamline the transfer of extensive data related to patient implants, which is currently a manual and time-consuming task.
When a customer moves from an existing Cardiology Information System to CCW, moving their existing device implant data is crucial. The device implant data needs to be stored securely on the system to facilitate future follow ups and tracking recalls and also for clinical compliance, safety and regulatory reasons.
At present there is no easy way to migrate this data into CCW, other than to do a bespoke data migration request or manually entering the implant data. We need a way to import this data.
Thankfully, we can reuse the National registry export information to to gather these data points.
The PM/ICD Registry Export for UK's NICOR already contains many data points pertaining to the patient's device and lead information that is presented in a standard csv file. Information can be mapped and imported into CCW, thereby enabling a way to bulk migrate the patient's device information.
Other vendors in the market already offer similar functionalities. To remain competitive and attract new customers, it is crucial to provide this feature. Without it, potential customers may be reluctant to switch from their existing platforms to ours.
Offering this functionality will position Centricity Cardio Workflow as a more attractive option for potential customers, helping to increase market share.
@Guest this is tracked under TFS req # 43818
The method of using the NICOR registry export format would work in the UK.
For other countries we would have to explore possibilities with respective National Registries