go to post Tani Frankel · Dec 28 It seems like you might have included in the question a different Transformation than the one the Warning is pointing at? As it refers to this one: osuwmc.Scott.FHIR.DemoOutboundHL7Message(and not: osuwmc.Epic.FHIR.DTL.FHIRResponseToPatient) And it seems like the Source of that Transformation is expected to be an HL7 message (with a DocType property) but for some reason, at least at runtime, the source is instead of type: osuwmc.Epic.FHIR.DataStructures.PatientSearch.Record In any case it looks like we're not seeing the wider picture in order to help you address this issue.
go to post Tani Frankel · Dec 27 Are you instantiating the 'target' variable?... It doesn't look like it, hence your Invalid Oref when trying to access the MRN property (unless you're sending it in ByRef, but in that case it seems not be an object either). So it looks like you were focused on the right side of your SET command, though the problem might be on the left side.
go to post Tani Frankel · Dec 25 Note in the meantime, it seems like Docker Login does still work.So for example I can still: docker login -u="<my user>" -p="<my password hash>" containers.intersystems.com WARNING! Using --password via the CLI is insecure. Use --password-stdin. Login Succeeded And then also: docker pull containers.intersystems.com/intersystems/irishealth:latest-cd latest-cd: Pulling from intersystems/irishealth 20043066d3d5: Already exists 8216b0a74174: Downloading [> ] 537.9kB/395.2MB 928364a257ac: Pulling fs layer dadfc3b0a484: Downloading [====> ] 433.5kB/5.24MB 122f1f35c4aa: Waiting So perhaps this can help you for now.
go to post Tani Frankel · Dec 25 Indeed the URL is available but when you try to login you get the error you mention.I'll report to our Support Thank you Dmitrii
go to post Tani Frankel · Dec 22 Hi Dmitrii, It shouldn't be too difficult. Yes, you can use Keycloak or other servers, and you'd need to make some definitions/configurations, indeed including scopes. I'll plan to get into this in another Article, but in the meantime you can see this example (including related GitHub repo and videos). Note this example uses our older Cloud managed service FHIR Server, but on the OAuth server side this behaves the same (I used auth0 there).
go to post Tani Frankel · Dec 9 And now there's already also this nice "Wizard" that helps with these definitions -
go to post Tani Frankel · Dec 8 Happy Birthday! 🎂 The InterSystems community wouldn't have been the same without... well... The Community!! Special congratulations to all the Community management team! You do such a great job for the benefit of all of us. And of course to all the members out there who contribute and take a part in this great place. Looking forward to the next 10 years!
go to post Tani Frankel · Sep 25 Wow! RESTFORMS was one of my all-time favorites! Great contributions all around! Well deserved recognition!
go to post Tani Frankel · Sep 17 Thanks @Ariel Glikman, great article, and samples on the OE app/GitHub repo. I believe anyone deploying IAM in a production-grade environment must consider and would greatly benefit from, using one of these options, and this would be an excellent jump board.
go to post Tani Frankel · Sep 2 Probably best you ask whoever sent you these classes. In general though %JSON.Adaptor has the %JSONFIELDNAME parameter, and not JSONNAME. Hence the error you got. [There is an existing package shared in the past on the Community, see for example here, with some similar functionality, that did have this JSONNAME parameter. But I don't know if this is related in any way to the code you have] [Note I also see you are using a %DynamicObject property ("Rationale"), and depending on what you expect to do with it, I don't know how well that will play with the %JSON.Adaptor export, per your use-case.]
go to post Tani Frankel · Aug 27 I'd look at JSONata. I played with it a while ago... And if you want to utilize our Python support, take a look at the Python edition of it: jsonata-python.
go to post Tani Frankel · Aug 14 In general (and messages and streams are just one example) there is a trade-off between more traceability and visibility vs. storage/space (and performance). QuickStream is indeed a mechanism used internally to address the performance and storage concerns, but, to complete this with a traceability option, there is also a dedicated Business Operation that can add the desired data - see Enhanced Debugging and the introduction of HS.Util.Trace.Operations. This simply adds more calls in the session, to this Operation which (could) include the stream data. The advantage of this is that you can turn it on or off, and you can control also the "level" of tracing. Take into account of course that this needs to be done ahead of what you want to trace/visualize, you can't "apply" this retroactively.
go to post Tani Frankel · Aug 7 By the way (apart from the /api/atelier/.../query API which I mentioned in my other response, which is a built-in API) there is also this custom API which @Evgeny Shvarov built - sql-rest-api, see also related article.
go to post Tani Frankel · Aug 7 This should work. What HTTP Method are you using POST (or GET)? What HTTP status are you getting - 200 OK (or 405 Method Not Allowed)?
go to post Tani Frankel · Aug 6 See using the Query API of the "Source Code File REST API" - Tutorial -> Performing an SQL Query Reference -> Query
go to post Tani Frankel · Jul 25 If you use the InterSystems CLI vis your OS shell, you can also simply run: #iris python instancename See the iris command docs (at least for some OSs).
