Thank you, very clear now!
- Log in to post comments
Thank you, very clear now!
Oh, Wow!
So many great answers! thank you @Stuart Strickland, @Chris Stewart , @Robert Cemper , @Ashok Kumar Thangavel
!
It was not obvious with $name and Class Parameter - now it is clear! Thanks a lot!
Thank you, @DC AI Bot - but your answer is not super relevant to the situation. I really want to store the global name in a class parameter and don't see what is wrong here.
Wow. Was the answer from AI right, @Scott Roth ?
It'd be great if we could alter the length of subscript per system. Sometimes the ability to momentarily get the value for a index of 1K+ values would be very benefitial
Thanks @Laura Blázquez García ! Do you want to share more details on how your app works?
This is great news, @Andreas Schneider !
That's impressive and persuasive! Thank you @Enrico Parisi !
Dear @Dean White , @Enrico Parisi: what to use better:
Do Body.%ToJSON(Request.EntityBody)or
do Request.EntityBody.Write(Body.%ToJSON())?
Thank you, @Tani Frankel !
This is useful through years!
Just adding here the snippet to add role to a user:
ClassMethod AddRoleToUser(user = "CSPSystem", role = "DB_USER_Read") As %Status
{
// Change to the %SYS namespace.
new $NAMESPACE
set $NAMESPACE="%SYS"
set status=##class(Security.Users).Get(user, .MyUserProps)
set $p(MyUserProps("Roles"),",",*)=role
set status=##class(Security.Users).Modify(user,.MyUserProps)
// Announce success.
if $$$ISOK(status) {
write !, "Roles for the user "_user_" were successfully modified."
}
Quit status
}Changed to an annoucement and added Job Wanted tag. Also take a look at Job Opportunity tag offerings.
Hi @Kevin Mayfield ! If you have docker on your laptop you can clone this Github project and start it in a docker - it starts InterSystems FHIR server (within IRIS for Health) automatically.
Thank you, @Arun Nadarasa !
In this case I suggest to submit a request in an ideas portal.
Is it very complex to develop a new DICOM adapter that will use global streams instead?
Thank you, @Ashok Kumar Thangavel ! I agree, you have my vote!
Thank you very much, @Enrico Parisi ! This looks like what I was looking for!
It is also looks as a perfect new generation for the deprecated %ZEN with:
set sc=##class(%ZEN.Auxiliary.jsonSQLProvider).%WriteJSONFromSQL(,sql)
Which only provides string, but not %DynamicArray so will not work for Spec First REST API.
@Arun Nadarasa - thank you for introducing the power of Lovable in Digital Health to many-many people! Including myself ;)
I can call after-install scripts, of course! Now this makes sense!
The only question - is it OK? :) It looks a little ... dangerous?
Thanks, Enrico! Namespace, of course! I prefer usualy the simplicity of having one Database in one Namespace if possible.
Your great answer doesn't answer though my question. The situation is: I deploy a package, which contains:
persistent class(es), data(generated ok, but could be different), WebApp (aka CSP app). I deploy a Role also, which will be used by the WebApp. Role need the access to database... Here is my question, which database resource do I provide to the role as I don't know the namespace the package will be installed by a potential user?
HI @Touggourt ! You can start e.g. from this template . So you can clone or use as a template this github repo.
When IRIS starts in this it is prepared to work with Python in any supported modes.
Here is the related article.
Thanks, @David Hockenbroch ! Looks ideal!
Thank you, @Ashok Kumar Thangavel ! Never used %WriteResponse() before.
May I ask you to provide the full method? I shared the persistent class in the updated post.
"Let's remember this tweet" ;)
I suggest we test the water in 6 month/one year. I believe all the frameworks(current or new AI-focused) will be a tool for AI to construct the frontend at least.
Same for the backend.
Or maybe we'll use "GPT Memory" concepts instead of relational/multi-model databases we used to work with.
Is it implemented yet? Found the need for it too :)
Yes! That'd be ideal!
Great article, @Timothy Leavitt ! I think it is questionable the recommendation not to use AI for the spheres you are not familiar with.
E.g. I'm not a frontend developer at all but the AI capabilities in AI generation are awesome and give me an opportunity to immediately have an MVP in frontend and also to build prototypes fast which was impossible in a preAI times.
also, thanks to @Semion Makarov swagger ui app is updated to support Swagger 3.1 version. and functionality is improved greatly! 
Great article! Thank you @Pablo Frigolett !
Also, if you develop in Docker there is an issue with server name, and my version of the same GetSpec method is:
ClassMethod GetSpec() As %DynamicObject
{
Set spec = {}.%FromJSON(##class(%Dictionary.CompiledXData).%OpenId("dc.Sample.v2rest.spec||OpenAPI").Data)
Set url = $Select(%request.Secure:"https",1:"http") _ "://"_$Get(%request.CgiEnvs("SERVER_NAME")) _ ":" _ $Get(%request.CgiEnvs("SERVER_PORT")) _ %request.Application
Set spec.servers = [{"url" : (url)}]
Quit spec
}Thanks to @Lorenzo Scalese !