The system we use to create reports saves the reports on the file system as study Instance UID and another copy as patient name.
So, when patient name contains such characters as "/", it becomes impossible to save report till patient name is manually edited on the server.
It seems there is no way to achieve this with current coercion options.
Any Ideas?
Thanks.
Remove/Replace a Character in Patient Name.
Re: Remove/Replace a Character in Patient Name.
What would you suggest for the coercion rule syntax that's suitable for something like this?
Re: Remove/Replace a Character in Patient Name.
My suggestion will borrow from existing rules.
For deletion of an unwanted character(s) something like "value->" where value replaces the wildcard * in the current delete value syntax could be used. e.g /-> removes the "/".
For replacement, we can do "value->new value". This is similar to the replace rule syntax where received/existing value is replaced. In this case, a real value replaces the wildcard *
You may even have one that removes/replaces all symbols e.g @->
Thanks.
For deletion of an unwanted character(s) something like "value->" where value replaces the wildcard * in the current delete value syntax could be used. e.g /-> removes the "/".
For replacement, we can do "value->new value". This is similar to the replace rule syntax where received/existing value is replaced. In this case, a real value replaces the wildcard *
You may even have one that removes/replaces all symbols e.g @->
Thanks.
Re: Remove/Replace a Character in Patient Name.
The suggested syntax seems to be a little ambiguous, so we are considering using the Regular Expression (RE) syntax for all string pattern matching related features. But the RE library seems to be too technical/complex for some users, and may not be trivial to implement?
Re: Remove/Replace a Character in Patient Name.
Thanks.
I must confess that the simplicity of Pacsone is one of its strengths, though I have used RegEx rules before without any problem especially when there are a few sample rules. It could be under an "advanced Rules" button that is not even visible by default.
For me, this is not a critical feature. We will do fine even without it.
I will leave it to your discretion - probably also based on available time and whether any other users desire such a feature.
Thanks.
I must confess that the simplicity of Pacsone is one of its strengths, though I have used RegEx rules before without any problem especially when there are a few sample rules. It could be under an "advanced Rules" button that is not even visible by default.
For me, this is not a critical feature. We will do fine even without it.
I will leave it to your discretion - probably also based on available time and whether any other users desire such a feature.
Thanks.