TrakCare Doesn’t Go Beyond the Start
Rating: 1 out of 10
IncentivizedUse Cases and Deployment Scope
It is used as a front end of one of our main products. Internally and externally it’s used heavily. It allows users to search our patient database and display SDA/HL7 information.
Pros
- Quickly get a front end working into patient indexes.
- Integrates with InterSystems products.
- Works with IE well.
Cons
- Extensibility of features.
- Custom JavaScript/HTML/CSS support is almost nonexistent.
- Source control has to rely on serialization of entire compiled package of TrakCare instead of individual edited files.
- Transformations should handle everything instead of just non system default code.
Likelihood to Recommend
Well suited if you have no developers and need something up quickly to let users get into patient data. But if you want to go beyond the layout, organization, or access of the application, it’s an uphill battle and doesn’t scale at all. If you want to be able to evolve the product, it’s not easy whatsoever.