 | DetectedIssue Class |
An issue raised by CDSS, Business Rules, or the persistence layer representing a constraint on the object
Inheritance HierarchyNamespace: SanteDB.Core.BusinessRules
Assembly: SanteDB.Core.Api (in SanteDB.Core.Api.dll) Version: 2.2.1
SyntaxThe DetectedIssue type exposes the following members.
Constructors| Name | Description | |
|---|---|---|
 | DetectedIssue |
Default ctor for detected issues
|
| DetectedIssue(DetectedIssuePriorityType, String, String, Guid) |
Creates a new detected issue with the specified field values
|
Properties| Name | Description | |
|---|---|---|
 | Id |
Gets or sets the identifier of the detected issue
|
| Priority |
Represents a detected issue priority
|
| Text |
Gets or sets the textual description of the detected issue.
|
| TypeKey |
The type of detected issue (a concept key) which can be used to classify the detected issue
|
Methods| Name | Description | |
|---|---|---|
| Equals | Determines whether the specified object is equal to the current object. (Inherited from Object.) |
 | Finalize | Allows an object to try to free resources and perform other cleanup operations before it is reclaimed by garbage collection. (Inherited from Object.) |
| GetHashCode | Serves as the default hash function. (Inherited from Object.) |
| GetType | Gets the Type of the current instance. (Inherited from Object.) |
| MemberwiseClone | Creates a shallow copy of the current Object. (Inherited from Object.) |
| ToString | Returns a string that represents the current object. (Inherited from Object.) |
Extension Methods| Name | Description | |
|---|---|---|
 | ConvertTReturn |
The purpose of this method is to convert object me to TReturn. Why?
Because if you have an instance of Act that actually needs to be a SubstanceAdministration we can't just cast
so we have to copy.
(Defined by ExtensionMethods.) |
| GetInstanceOfTDomain |
Gets an instance of TDomain from me
(Defined by ModelExtensions.) |
RemarksIn SanteDB, a detected issue is used to represent a business constraint violation (opposed to a software exception) which has impacted the ability of the SanteDB server software to process the requested action. Examples of detected issues can include:
- Assigning an incorrect / unbound code to a field
- Adding an inapporpriate relationship type (i.e. Mother linking an Organization to a Person)
- Inappropriately assigning an identifier out of scope (i.e. a GLN on a Person)
- Business rules trigger violations
In SanteDB any plugin can throw a DetectedIssueException wrapping a collection of issues, in the core iCDR and dCDR services, detected issues are commonly raised by:
- The persistence layer (validating relationship types, identifier scopes, etc.)
- The data quality business rules trigger (validating in-country minimum data sets, etc.)
- The JavaScript business rules service (whenever a business rule validate() or trigger event throws an exception)
- The Clinical Decision Support / CarePlanner (when raised by a protocol)
See Also