Hi,
The organization that I work for has computer systems that are certified after code reviews. Now that we are planning to use Corticon there is no longer any code. We just have rule sheets, rule flows and system generated documentation. I'm expected to explain to our certification bureau how Corticon does things and basically tell them how they can do their audits in this non-code environment.
Does anybody know how to expose the nuts and bolts of a Corticon decision service in a way that is equivalent to a traditional code review?
Thank you,
Ollie
1. Make sure that every condition and action is documented with a natural language equivalent (this makes it easier for a non Corticon person to understand the intent of every rule – it’s also very useful in clarifying your own understanding of what the rules are supposed to do). You can even create them in several different languages – particularly useful if you are based in Europe.
2. Make sure that every rule column has one or more rule statements attached to it – you can attach different rule statements with different amounts of detail and post them to different objects to generate more or less detail on demand. The audit trail produced in this fashion provides the equivalent to “code”. There’s also a new brms.proprties setting that allows you to control whether info, warning or violation messages are returned.
3. Use the “report” function in Corticon to generate an HTML representation of all of the rules (or vocabulary or test cases). This can then be viewed by people who do not have a copy of Studio.
4. For the more adventurous you can also use the Corticon rule modeling APIs to introspect the rule model and generate your own custom audit review report (see example below).
Hi,
The organization that I work for has computer systems that are certified after code reviews. Now that we are planning to use Corticon there is no longer any code. We just have rule sheets, rule flows and system generated documentation. I'm expected to explain to our certification bureau how Corticon does things and basically tell them how they can do their audits in this non-code environment.
Does anybody know how to expose the nuts and bolts of a Corticon decision service in a way that is equivalent to a traditional code review?
Thank you,
Ollie
Flag this post as spam/abuse.
1. Make sure that every condition and action is documented with a natural language equivalent (this makes it easier for a non Corticon person to understand the intent of every rule – it’s also very useful in clarifying your own understanding of what the rules are supposed to do). You can even create them in several different languages – particularly useful if you are based in Europe.
2. Make sure that every rule column has one or more rule statements attached to it – you can attach different rule statements with different amounts of detail and post them to different objects to generate more or less detail on demand. The audit trail produced in this fashion provides the equivalent to “code”. There’s also a new brms.proprties setting that allows you to control whether info, warning or violation messages are returned.
3. Use the “report” function in Corticon to generate an HTML representation of all of the rules (or vocabulary or test cases). This can then be viewed by people who do not have a copy of Studio.
4. For the more adventurous you can also use the Corticon rule modeling APIs to introspect the rule model and generate your own custom audit review report (see example below).
Hi,
The organization that I work for has computer systems that are certified after code reviews. Now that we are planning to use Corticon there is no longer any code. We just have rule sheets, rule flows and system generated documentation. I'm expected to explain to our certification bureau how Corticon does things and basically tell them how they can do their audits in this non-code environment.
Does anybody know how to expose the nuts and bolts of a Corticon decision service in a way that is equivalent to a traditional code review?
Thank you,
Ollie
Flag this post as spam/abuse.
Flag this post as spam/abuse.
Olaf Janssens
Meridian Health Plan
Technical Business Analyst
777 Woodward Ave, Suite 600
Detroit MI 48226
www.mhplan.com
p. 313-324-3700 x1126
IMPORTANT: This email may contain confidential information, some or all of which may be protected health information as defined by the federal Health Insurance Portability & Accountability Act (HIPAA) Privacy Rule (45 C.F.R. Part 160; Subparts A and E of Part 164). This message is intended for the exclusive use of the individual or entity to whom it is addressed and may contain information that is proprietary, privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient (or an employee or agent responsible for delivering this email to the intended recipient), you are hereby notified that any disclosure, dissemination, distribution or copying of this information is strictly prohibited and may be subject to legal restriction or sanction. Please notify the sender by telephone at (313) 324-3700 to arrange the return or destruction of the information and all copies.
[/collapse][/collapse]