go to post Ashok Kumar · Feb 7 Hello @Ali Chaib I could find the relevant SDA class resource HS.SDA3.Task for the FHIR Task. AFAMA, there is no built in DTL or relevant FHIR model class available to transfer SDA to FHIR resource. for now, You can create a your own FHIR model class for Task and create a customized DTL under HS.Local.FHIR.DTL. package use the SDA3.Task as destination class for transformation.
go to post Ashok Kumar · Feb 6 Yes, the journal doesn't contain that information and maybe it's operational overhead to hold this additional information. As always using the program debugger and verify the routine. This is a general question, as I mentioned earlier there are multiple is routines and classes executed and the global are set via indirection, Xecute the predefined code and usual direct set. Thanks for your response @Vic Sun
go to post Ashok Kumar · Feb 6 Hello @Vic Sun To summarize the situation, when executing a program, it calls various routines and classes, the expected global values is set somewhere in between the flow. I need to determine where a specific global was set. The journal contains details like process ID, database values (old and new), and more. So, Maybe If the journal includes an additional entry in the format of label+offset^routine indicating where the global was set it's easy to track for my case.
go to post Ashok Kumar · Feb 3 Hello @JIM WHEELER Seems you're trying to store the error message. If yes, You can use $SYSTEM.Status.GetErrorText(status) to get the error text of the and store. If you want to convert the list build values as a string. use ##class(%Utility).FormatString() method USER>Set str = ##class(%Utility).FormatString($LB(1,2)) USER>zw str str="$lb(1,2)"
go to post Ashok Kumar · Feb 3 Hello @Deepa Shahi You can customize the SDA3 package. A native discrete SDA class is available to convert the data's from HL7 to FHIR and vise versa. In this case, HS.SDA3.Encounter is the SDA class. There is an additional editable extension class( "HS.Local.SDA3.EncounterExtension" - Encounter) available in these primary SDA classes to customize data elements. You can define all your required data elements in to this extension class and compile the package. If you're using the SDA to FHIR conversion by DTL native approach. Customize the DTL You have to copy the existing DTL "HS.FHIR.DTL.SDA3.vR4.Encounter.Encounter" to "HS.Local.FHIR.DTL.SDA3.vR4.Encounter.Encounter". Before customizing DTLs, you need to specify a single package for all customized DTL classes. InterSystems recommends naming the class package: HS.Local.FHIR.DTL. Now you can modify the newly copied DTL based on your requirement. this newly created DTL is not invoked by default. So, execute below code in your FHIR enabled namespace. The FHIR API classes use this HS.Local.* DTL packages while generating the resources ("Encounter" ) set status = ##class(HS.FHIR.DTL.Util.API.ExecDefinition).SetCustomDTLPackage("HS.Local.FHIR.DTL")
go to post Ashok Kumar · Jan 31 Hello @Gabriel Santos AFAIK, The required property keyword works on literal, Collection, stream, serial, object valued properties except the %DynamicArray and %DynamicObject. Because by default the property methods(Getter) was created and it assign the values for %DynamicArray is "[]" and "{}" for dynamicObject even though if you assign empty string it overwrites it. so, The %ValidateObject() doesn't include these two objects for validation.
go to post Ashok Kumar · Jan 24 As you know the swagger is used to design the API documentation first, and then build the REST API based on that design. IRIS or other API systems don't inherently know about the payload, the return response, or the specific responses for status codes like 200, 400, or 500 unless it's specified. You're right about the traditional approach. Creating REST services manually doesn't have knowledge of these details. It generates the Swagger documentation based on the information available in the UrlMap and the class method in the dispatch class. Add your comments on top of the class method (meta data details) will be set into the description in swagger Spoiler If you want your API to be well-documented, it’s better to follow a spec-first approach, as this approach captures crucial details like paths, method types, descriptions, path parameters, query parameters, and responses. Thanks! /// The comment added for generated for swagger 2.0/// return type is %String/// Two path parameters/// one query parameterClassMethod test(id As %String, cid As %String) As %String{ return 1} Swagger: "/test": { "get": { "operationId": "test", "description": " The comment added for generated for swagger 2.0 return type is %String Two path parameters one query parameter ", "x-ISC_ServiceMethod": "test", "x-ISC_CORS": true, "responses": { "default": { "description": "(Unexpected Error)" }, "200": { "description": "(Expected Result)" } } }
go to post Ashok Kumar · Jan 23 Hello @Martin Nielsen If you're mentioned the Return types( %Status or %Stream.Object) those are is IRIS specific and swagger 2.0 doesn't have those types . It has "response" object in swagger information/you have to define the response. ex: {"responses":{"200":{"description":"Successfully retrieved user","schema":{"$ref":"#/definitions/User"}},"404":{"description":"User not found"}}} Path Parameters are documented by default ex : "/mytest/{userid}" "summary" and "description"- you can use this OpenAPI properties to add description and additional information about the classmethod. Please refer the below Swagger 2.0 sample. note: If you're using spec-first approach. You need to do all the changes in .Impl class not in .disp class. Because .disp is generated class and it will be overwritten once .spec class compiled(updating swagger). Swagger Spoiler { "info": { "title": "", "description": "", "version": "", "x-ISC_Namespace": "LEARNING" }, "basePath": "/aktest", "paths": { "/mytest/{userid}": { "get": { "summary": "the return type is %Status and there are few changes need to be done manually.", "description": "testing apis", "parameters": [ { "name": "userid", "in": "path", "required": true, "type": "integer" } ], "operationId": "test2", "x-ISC_ServiceMethod": "test", "x-ISC_CORS": true, "responses": { "default": { "description": "(Unexpected Error)" }, "200": { "description": "(Expected Result)" } } } } }, "swagger": "2.0"} .disp class Spoiler /// Dispatch class defined by RESTSpec in myapptest.specClass myapptest.disp Extends %CSP.REST [ GeneratedBy = myapptest.spec.cls, ProcedureBlock ]{ /// The class containing the RESTSpec which generated this classParameter SpecificationClass = "myapptest.spec"; /// Ignore any writes done directly by the REST method.Parameter IgnoreWrites = 1; /// By default convert the input stream to UnicodeParameter CONVERTINPUTSTREAM = 1; XData UrlMap [ XMLNamespace = "http://www.intersystems.com/urlmap" ]{<Routes> <!-- the return type is %Status and there are few changes need to be done manually. --> <Route Url="/mytest/:userid" Method="get" Call="test" Cors="true" /></Routes>} /// the return type is %Status and there are few changes need to be done manually.ClassMethod test(puserid As %String) As %Status{ Try { If ($number(puserid,"I")="") Do ##class(%REST.Impl).%ReportRESTError(..#HTTP400BADREQUEST,$$$ERROR($$$RESTInvalid,"userid",puserid)) Quit Set response=##class(myapptest.impl).test(puserid) Do ##class(myapptest.impl).%WriteResponse(response) } Catch (ex) { Try { Do ##class(myapptest.impl).%ReportRESTError(..#HTTP500INTERNALSERVERERROR,ex.AsStatus(),$parameter("myapptest.impl","ExposeServerExceptions")) } Catch { Do ##class(%REST.Impl).%ReportRESTError(..#HTTP500INTERNALSERVERERROR,ex.AsStatus(),$parameter("myapptest.impl","ExposeServerExceptions")) } } Quit $$$OK} }
go to post Ashok Kumar · Jan 21 Hello @Pietro Di Leo AFAIK, There is no direct execution of the IndexKeyOpen and other generated methods in python. We can write a wrapper method to run those methods. Class pylearn.NewClass2 Extends %Persistent { Property Code As %String(MAXLEN = 50) [ Required ]; Index CodeIdx On Code [ Unique ]; ClassMethod RunCode() [ Language = python ] { import iris iris_obj = iris.cls(__name__).GeObjByIdx("CodeIdx","A212") print(iris_obj.Code) } ClassMethod GeObjByIdx(IndexName, ID) { Return $ClassMethod(,IndexName_"Open",ID) } }
go to post Ashok Kumar · Jan 13 Hi @Enrico Parisi Yes. Lock is crucial to achieve the ACID complaint and avoid the concurrency control issues.
go to post Ashok Kumar · Jan 13 Hello @omer The above same is ACID complaint when using transactions. It will be reverted to old value under transaction rollback. However, The counter values are incremented by $Increment and $Sequence are will not changed even rollback. LEARNING>w ^myTracker("onSomething") 1 LEARNING>ts TL1:LEARNING>s ^myTracker("onSomething")=12 TL1:LEARNING>w ^myTracker("onSomething") 12 TL1:LEARNING>trollback LEARNING>w ^myTracker("onSomething") 1 LEARNING> $Increment and $sequence LEARNING>write ^myTracker("onSomething") 1 LEARNING>tstart TL1:LEARNING>do $Increment(^myTracker("onSomething")) TL1:LEARNING>write ^myTracker("onSomething") 2 TL1:LEARNING>trollback LEARNING>write ^myTracker("onSomething") 2 LEARNING>
go to post Ashok Kumar · Dec 16, 2024 Hello @Yaron Munz I've enabled the "%System/%Login/JobEnd" in Audit events. I opened a new terminal(new process) and I terminate the process via Management portal. However, I haven't seen any entry in the Audit log.
go to post Ashok Kumar · Dec 12, 2024 :clear deletes all the commands in that particular process/recall buffer. If you open another terminal and :history shows all commands. So, I thought some native commands exist like :clear to delete the commands history permanently. !del %USERPROFILE%\.iris_history - yes, we can the use the file system commands. Thanks!
go to post Ashok Kumar · Dec 12, 2024 Thanks Chris, It works. However, There is no command to do it from terminal itself?
go to post Ashok Kumar · Dec 11, 2024 Thanks for pointing the solution. By using this integer we can get the request if test is 1or response test=2 or test = 3 headers. However, As of my understanding we didn't get both request and response at the same time.
