Proper configuration of the Tolven software can result in fully functioning CPOE that includes (but is not limited to): 1 creating catalog of orderable services with both standard and local nomenclature 2) Documenting instances of ordered services; input forms include field constraints, calculated fields, branching logic 3) Creating rules to detect conflicts and/or duplicates across ordered services 4) instantiating of ordered services and resulting state changes 5) transmitting ordered services to other systems 6) documenting and transmitting changes to ordered services 7) implementing rules for enterprise formula constraints 8)creating work lists of ordered services for appropriate clinical personnel 9) receiving results of ordered services and linking those results to the original orders.
None of these application functionalities have been configured by Tolven although we expect to have a (highly domain specific) set of orderable services that will exhibit most of the functionality described above for one of our clients within the coming months. That functionality will be integrated into the core Tolven open source offering but may have little relevance to clinicians in other domains.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Greetings,
I am a technical audience but wanted to find out feature wise what are the CPOE capabilities of tolven..
What does it offer currently, what is in the immediate pipeline.
Regards,
gnaval.
Proper configuration of the Tolven software can result in fully functioning CPOE that includes (but is not limited to): 1 creating catalog of orderable services with both standard and local nomenclature 2) Documenting instances of ordered services; input forms include field constraints, calculated fields, branching logic 3) Creating rules to detect conflicts and/or duplicates across ordered services 4) instantiating of ordered services and resulting state changes 5) transmitting ordered services to other systems 6) documenting and transmitting changes to ordered services 7) implementing rules for enterprise formula constraints 8)creating work lists of ordered services for appropriate clinical personnel 9) receiving results of ordered services and linking those results to the original orders.
None of these application functionalities have been configured by Tolven although we expect to have a (highly domain specific) set of orderable services that will exhibit most of the functionality described above for one of our clients within the coming months. That functionality will be integrated into the core Tolven open source offering but may have little relevance to clinicians in other domains.