Research Rhapsody Project Needed
Budget: $30 – $250 AUD
I’m conducting an academic study on healthcare interoperability and need a complete, decommissioned (or demo) Rhapsody Integration Engine project that you personally own or have written permission to distribute.
What I’m after is the real-world structure of a live system without the live data:
• A full project export in .rlc, .zip or any equivalent archive that can be imported straight into Rhapsody
• Multiple HL7 interfaces already wired: ADT, ORM and ORU are a must, and I’d like the SIU feed present as well
• Genuine transformation logic—custom JavaScript, filters, data mapping rules, code tables, or other scripting you built for the original environment
• Several routes or channels showing how messages flow end-to-end
Strict data requirements
All customer, patient and organisation identifiers must be stripped, obfuscated or replaced with dummy values before you send the file. The project should contain no proprietary or confidential material—only the scaffolding, scripts and configuration that demonstrate how the engine was set up.
Acceptance
I’ll import the archive into a clean Rhapsody workspace and verify that:
• Interfaces compile and open without missing components
• Sample test messages can traverse each route successfully
• No residual PHI, real names, or internal IPs remain
If you already have a retired project that fits, this should be a straightforward share; if you need to anonymise first, I’m happy to agree a milestone for that step.
What I’m after is the real-world structure of a live system without the live data:
• A full project export in .rlc, .zip or any equivalent archive that can be imported straight into Rhapsody
• Multiple HL7 interfaces already wired: ADT, ORM and ORU are a must, and I’d like the SIU feed present as well
• Genuine transformation logic—custom JavaScript, filters, data mapping rules, code tables, or other scripting you built for the original environment
• Several routes or channels showing how messages flow end-to-end
Strict data requirements
All customer, patient and organisation identifiers must be stripped, obfuscated or replaced with dummy values before you send the file. The project should contain no proprietary or confidential material—only the scaffolding, scripts and configuration that demonstrate how the engine was set up.
Acceptance
I’ll import the archive into a clean Rhapsody workspace and verify that:
• Interfaces compile and open without missing components
• Sample test messages can traverse each route successfully
• No residual PHI, real names, or internal IPs remain
If you already have a retired project that fits, this should be a straightforward share; if you need to anonymise first, I’m happy to agree a milestone for that step.