Thank you Marc

I'm Impressed. That assumes that a word does not change meaning based on the characters to the left or right. So I assume you have taken that into account in your solution as I believe that Chinese is one of those languages that can mean different things depending on the surrounding words and even tone. But then, China is not part of NATO, so the question is academic.

How about French? Does anyone have a French example of conveying masculine/feminine attributes in the resultant interpreted message? i.e. how do you ensure you get your Le's and La's right?

Ok, now it's me being silly. I suspect there is no shorter version of this code, so well done to the winner.

You can make it smaller by removing the #dim, which is not required.

The only time I use #dim is if I am working with a class that I have got to via an object chain:

set class=##class(%Dictionary.CompiledClass).%OpenId("MyClass") for i=1:1:class.Properties.Count() set tProp=class.Properties.GetAt(i)  write !,prop.Name

In that case, I will use '#dim tProp as %Dictionary.CompiledProperies' as I don't remember all of the properties in the CompileProperties class. Once the code works, I remove the #dim.

If you are a masochist and like a little pain, here is a lengthy description of another scenario where I use #dim where I have many very similar classes in content, and I use a lot of $clssmethods and $properties in my code. 

Let us assume you have three message classes. The message classes will have some properties that are common to all message classes, and the message classes differ only in the fields they contain that are derived from the source system that created the message:

The base properties are the Create/Process/Completed TimeStamps, RequestFHIRJSON, ResponseFHIRJSON, RequestHL7Message, ResponseHL7Message, FileDirectory, SourceFileName, ResponseFileName, HTTPMethod, HTTPResponseCode, RequestStatus, MessageStatus, MessageTextNotification and a few others.

The HL7 or FHIR message that is created by a Data Transform (DTL) that transforms data in the source database into the target HL7 or FHIR message

The Message also contains the HL7 or FHIR response message (Operation Outcome in the case of FHIR, ACK/NACK for HL7)

Yous have methods to CreateMessage(), UpdateMessage(), GetNextMessage(), Complete Message(), ResendMessage(), PurgeMessages()

The variable properties in my three examples are:

1) PatientID for Message 1

2) PatientNumber, VisitNumber, EpisodeNumber, ActivityDate for Message 2

3) Hospital Folder Number in Message 3

The Methods I have listed all contain $classmethod calls, and I don't really need to worry about the fields specific to the type of message. If I am creating a message or updating a message, I pass an array of DataTypes into the method where the 'key' in the array is the property name, and the 'Value' is the value for that property.

I do use the %Dictionary.CompiledClass definition for the Message Class definitions so that I can determine whether the Property referenced in the Array of Datatypes is a %Library Data Type, a Foreign Key or Designative reference to a value in another class or a Collection/Array/List so that I know whether I am just setting the property value in my message object to the value in the Array of Property Values or if the property value is the ID of an object in another class in which case I will use a SetObjectIdAt() on the value and in the case of the List/Array Collections I either use SetAt() or InsertAt(). As I am using the CompiledClass Dictionary reference, I check to see if the property in the Array of Datatypes exists in the properties of the message class. However, in my Business Process, I want to get the Message fields because they will tell me what Class/Table I will access using the data supplied to retrieve the source record fed into the DTL to generate the FHIR/HL7 message. 

The Business Process has been passed an Ensemble Request message with the MessageId returned by the GetNextMessage() method, which my Business Service calls. The Business Service has a property "Message Queue Class Name" configured when I add the service to the production.

The Business Process Opens the Message Object and in that case I use a #DIM purely that when I use 

set obj=$classmethod({message_Queue_Class_name},"%OpenId",{Message_Id})

set tPatientId=obj.PatientId, and because I have used #dim the editor will provide a list of property names as I type in obj. and that makes it easier to select the field that I want to access. I have used simple examples for the variable fields in my different message class examples. Still, as my Message Queue Classes have about 15 common Properties, it is useful to have that IntelliSense functionality so that I don't have to keep remembering whether my common property name was SourceFHIRMessage or SouirceMessageFHIR. 

Once my code works, I comment out the #dim line rather than remove it so that if someone else has to maintain my code, they can uncomment the #dim statement. It may then help them with the Intellisense on the Property Names on the class being Manipulated.

Hi Robert

I desperately need an example of Angular using REST to talk to a FHIR server to convince the company that we should be using Iris for Health and Angular for our upcoming developments. The issue is I don't know angular, I understand Rest and I understand FHIR. How can I get up and running in Angualr in the next 3 days.

Nigel

Hi

I'd be interested in participating. An opportunity to work with a technology that I am very aware if but has not been a requirement in the work I do though HST has built an Operational Data Store.and we have a BI analyst who uses Deep See (Ensemble 2018). And Analytics in IRIS has gone to a whole new level. So yes I would like to participate. On IRIS?

Nigel

Hi Andre

I have read your article and I think that it is worthy of being included in this thread as you speak many truths. I am sure that many people work with technology, from the Customer Project Managers, the Business Analysts, the Team Leaders, the Scrum Master, the Senior Developers, Junior Developers, Testers, Customer UAT testers, and ultimately the Users of the resultant Technology Solution who view their role in the chain with Blinkers and work on the basis that as long as they do their job properly (and that is a word that can mean many different things) and are either unconcerned about the people who fill the other roles in the chain or view them as a necessary evil. But I also believe that there are technologists who are very conscious of the fact that they are an important element in the overall delivery of a solution. It is very rare to find people who can wear the hat of all of the players in this chain. I have met maybe 3 people in my entire career who just stood head and shoulders above everyone else in their ability to communicate and understand the needs and requirements of the customer,  translate those requirements into a set of tasks for the Business Analysts to prioritize, document, create the project scope and timeline, write requirement specifications that can be understood by the customer and the development team, be able to sit with the senior developers and discuss the possible approaches to crafting a solution, who can clearly identify which tasks should be handled by the senior developers and those that should be delegated to the more junior developers, create testing plans for the testers and the documentation writers and ultimately guide the Customer UAT team through the stringent test scenarios to ensure that the application does what was requested, does not crash, does not present the user with an explosion of colour and animation and finally go back to the customer and get that all-important sign-off so that the invoicing and payments can be finalised. Some of us have been lucky enough to have been assigned to a project where we were able to interact with the customer, understand their business, understand their pain or their ambitions, then take that knowledge and produce the requirement specifications, technical process flows, choose the software elements, write the code that pulls all of the components into a functioning whole, documents their code such that future developers who have to work with that code can do so without messing it up because they are unaware that a statement in line 23 of 5000 lines will inadvertently cause the logic on line 2356 to take an unexpected step to the left and render the program unusable. Very few developers get to spend time with the quality assurance staff and ultimately the users who have to use the application to do their jobs and be able to go home without a blinding headache and a sense of dread that tomorrow they are going to have to fight with the application to get the printout or that all-important "Your data has been saved. Click OK to proceed" popup.  

I have seldom met a programmer who will concede that their code is not as good as the person coding next to them, or for that matter finding a developer who can gracefully and politely read some truly awful code of another developer and take the time to work with that bad developer and help them become a better programmer without inadvertently step on 1 f 20 emotional and ideological traps that arise in every one of these encounters. Or maybe I would use the analogy of the McDonalds Ice-cream specialist who was born to whip up the most perfect McFlurry who has to stand and watch a steady stream of ice-cream servers who don't give a damn and will be leaving in a month to go and pour soda at Wendy's. 

For the last 50 years software creators, whether they be individuals or technology companies, have discussed, and theorized, and consulted psychologists and time-management experts, and even astrologers to come up with the definitive guide to creating perfect, absolutely perfect, application. Entire libraries of books and templates and methodologies and Predictive Indicators intended to match the right person to the right role and despite those 50 years and the brilliant, practical, theorists and technologists who have contributed, with dedication and fervor to this topic, And yet, for every model that has emerged from these think tanks, 100 bad applications are spilling out the doors of the technology companies.

And I haven't even started on the external forces, the project managers, the customer relations manager, the accountants, the middle managers, and worst of all the salesmen who, in just doing their jobs, manage to inflict sufficient damage to the 'plan' thus guaranteeing that the final product will be ....less.

But then you encounter a group of people who have formed themselves into a community, a 'Developer Community', who come from a myriad of different backgrounds, skills, methodologies, personalities, and socio-economic, gender-based cultures who miraculously have one thing in common. They love to code. Their hearts soar when they interact with a user who says 'Thank you because of some modification that they have made that has made that user's life just that little bit better. And all of us have at some time or other written a bad piece of code or have struggled to fit into the 'TEAM', or had to deal with a salesman who has sold unrealistic solutions and unachievable timelines to a customer who in reality didn't actually know what they actually wanted to start with. We have seen it all, we have notched up successes and strive hard to forget the failures and yet we go to bed at night and we dream of tropical islands with dancers wrapped in fine silks with pet tigers on leads and woken up the following morning with 5 pages of code written vividly on the insides of their skulls and in a blinding flash of light they know that they have cracked it. The mists of possibilities and uncertainties and intrusions and indecision that has plagued them for the previous 4 weeks have overnight coalesced into the 'Perfect' solution. Their fingers are already tapping at their laptops as they eat their breakfast and for the next 8, 18, 80 hours magic flows from their fingers into that IDE that is the interface between their imagination and the architecture that will swallow up their code and compile it into the module and voila! It's done, and it's beautiful.

And then we go home and get up the next day and do it all again. And as we create solutions we come to our community and we bounce ideas off each other, we seek out the nuggets of knowledge and experience from our friends who went through the process of being the first person to master a technique or understand a piece of functionality that is almost incomprehensible to most of us because or minds might not be wired in such a way that understanding that functionality was as easy as watching the Eurovision song contest without crying.

What we all share in common though are years and years of tuning our coding styles, learning and absorbing emerging technologies, developing the skills to share our knowledge with the people we work with without making them run from the room sobbing because you have been too brutal in your appraisal of their work and it is through a community like ours that so many of us have become the skilled and dedicated developers that we are.

What I do know is that generally speaking, I have met more developers who have been able to help the Business Analysts understand the requirements, ask the right questions of the customer to find out what they actually need, pacify the project managers that their agile, and scrum, and Jira, and storyboards will get to the finish line without incurring penalties for late delivery. Who find the time to document their code knowing that no matter how well it is written it is going to take another developer some time to work out what you have written and how it fits into the bigger picture and finally, one day, they get to meet the user who is using that application who turns round and comments that this application has helped them get their work done quickly and efficiently, that doesn't shower them with pompous popups asking them how they could be so stupid to put a text letter into a numeric field. 

We may not be able to ensure that every element in the chain is going to work as expected and that ideas and requirements don't occasionally get twisted in translation nor make every single user equally happy but we can control the space that we occupy and we know what we are doing and we have adopted different coding styles over the years and we find our selves at a point where we believe that we can layout a template, a structure, a developers ethical code and produce a set of standards and conventions on which we all (give or take) agree, if followed, will stand a chance of guaranteeing that the programs we write work, are readable and maintainable and when fitted into the whole will generate an application that works, is good, beautiful even.

We take pride in our community. We welcome the input of the outside world, we like to learn and experiment and listen to the experiences of our comrades and when we are in Boston we will gather in a fairly dark room and drink a little too much and listen and watch as one of ours demonstrates his latest little app or tool or plugin and it makes us happy and we feel very much at home.

Nigel. 

When i run the following:

set srv = $system.external.getServers()

write srv.%ToJSON()
["%DotNet Server","%IntegratedML Server","%JDBC Server","%Java Server","%Python Server","%R Server","%XSLT Server"]

R does appear

Nigel

Hi Ben

I certainly would like to join the Python EAP. I was actually sent an invite but it slipped through the gap and I had communicated with Eduard to issue another Invite. I have already installed the InterSystems IRIS 2021.1 PYTHON kit and I just need a license. At Anastasia's recommendation, I sent a request to Bob to get a license. I don't know if it's too late to join the current EAP as gather there will be another one but if I can join in the current one then that would be great

Hi Ben

Yeah, I added the comments about APL because I just happened to notice it in Wiki while looking at R and it reminded me of my Actuarial days. It was a curious language being almost entirely symbolic in nature. The standard "Hello World" program that every language tutorial teaches was something more like 

I learned it in 1981 and I see that there have been releases of APL2 and so I guess that somewhere someone is using it (probably in Mathematical Modelling which is what many Actuaries do instead of designing Insurance Policies and staring at Life Expectancy Tables which was what Actuaries did in those day) and I think that a language like Julia (which I have also downloaded and played with a few months ago is much more suited to Pure Math). Can I ask a question, I notice that Python is an Interpreted language like ObjectScript. Was that part of the decision to include it into InterSystems IRIS (and also that it is one of the most popular languages on the Top 10 language list) based on the fact that it could ultimately be compiled down to .obj code?

That sounds really cool. I have a friend who had a house in Cape Town and he had installed Solar Panels, water collection systems,  and everything in his house from his music system, alarm system, gates, garage doors, lights, curtains, fridge were all controlled through an app on his phone. His solar panels and storage cells effectively covered all of his electricity needs and his electricity meter for City Power cost about R5 a month

Hi Utsavi

How are you doing with this challenge. Have you got a working solution yet? If so please can I have a look.  If I have managed to help get you to where you need to be please mark one of my replies as an acceted answer

Thanks

Nigel

Olga, I love you! and my InterSystems Logitec Camera arrived yesterday and it is beautifully designed and solid and take great pictures and videos so that along with my JBL clip and my InterSystems socks are my 3 most prized possessions at the moment so the opportunity to earn extra points and I'm looking forward to the next great reward that we can aim for when redeeming points. 

Hi Utsavi

I have sent you an email with the classes.

I have managed to get all of the scemas to be generated correctly and exported to JSON correctly. the only issue is that the if I just use the class name as the 'key' in the array you will only get one instance of each schema however if I append the counter to the classname then it will create multiple instances of each schema in the class

{
  "%seriesCount": "1",
  "parentId": "Parent226",
  "parentName": "Example: 228",
  "schemas": {
    "Contact12": {
      "%seriesCount": "1",
      "contactGivenName": "Vincent",
      "contactSurname": "Chesire",
      "contactPhoneNumbers": {
        "Phone-1": "+2704 435 4225"
      }
    },
    "Contact3": {
      "%seriesCount": "1",
      "contactGivenName": "Marvin",
      "contactSurname": "O'Brien",
      "contactPhoneNumbers": {
        "Phone-1": "+2796 757 9897",
        "Phone-2": "+2796 079 6474",
        "Phone-3": "+2721 225 2055"
      }
    },
    "Patient7": {
      "%seriesCount": "1",
      "patientId": "PAT-000-494",
      "patientDateOfBirth": "2020-05-31T02:44:39Z"
    },
    "Practitioner11": {
      "%seriesCount": "1",
      "practitionerId": {
        "%seriesCount": "1",
        "practitionerId": "PR005",
        "practitionerTitle": "Dr.",
        "practitionerGivenName": "Al",
        "practitionerSurname": "Beatty",
        "practitionerSpeciality": "Orthopedics"
      },
      "practitionerIsActive": false
    },
    "Practitioner4": {
      "%seriesCount": "1",
      "practitionerId": {
        "%seriesCount": "1",
        "practitionerId": "PR0043",
        "practitionerTitle": "Dr.",
        "practitionerGivenName": "Maureen",
        "practitionerSurname": "Gomez",
        "practitionerSpeciality": "Orthopedics"
      },
      "practitionerIsActive": true
    },
    "Practitioner6": {
      "%seriesCount": "1",
      "practitionerId": {
        "%seriesCount": "1",
        "practitionerId": "PR0099",
        "practitionerTitle": "Prof.",
        "practitionerGivenName": "Pam",
        "practitionerSurname": "Russell",
        "practitionerSpeciality": "Orthopedics"
      },
      "practitionerIsActive": false
    },
    "Practitioner8": {
      "%seriesCount": "1",
      "practitionerId": {
        "%seriesCount": "1",
        "practitionerId": "PR0086",
        "practitionerTitle": "Mr.",
        "practitionerGivenName": "Debra",
        "practitionerSurname": "Zevon",
        "practitionerSpeciality": "Peadiatrics"
      },
      "practitionerIsActive": true
    },
    "Reference1": {
      "%seriesCount": "1",
      "referenceId": "Reference-419",
      "referenceText": "UMG]QX/&V1GLLCN ? \"RV[$IUYCQM-]]+7HSP:[N%MG\\V!L)P><>A'4>?7?,.0N*,UB( \\4)J!$_,X35D;S=61V?=SJ<,!&5P",
      "referenceOID": "8.11.0.54.18"
    },
    "Reference10": {
      "%seriesCount": "1",
      "referenceId": "Reference-423",
      "referenceText": "\"A/#VZZ?<=5E.'BZT<6^DQ!I65JU'+GB/3T[2+II9N7W8EUKHRWS;1RZM&2(A)",
      "referenceOID": "7.17.7.19.18"
    },
    "Reference13": {
      "%seriesCount": "1",
      "referenceId": "Reference-424",
      "referenceText": ",L^2SP.UY\"+'Y;OAG&:JF^36U6@-D\"VBQ3,*V<+UP4(-O>CX?5^#*A]ZTNK@G, )TW\"^)<,=92?O!:",
      "referenceOID": "4.19.5.89.7"
    },
    "Reference14": {
      "%seriesCount": "1",
      "referenceId": "Reference-425",
      "referenceText": "<E;)F5#R0(VO)+_KQ?)D",
      "referenceOID": "6.13.8.21.14"
    },
    "Reference15": {
      "%seriesCount": "1",
      "referenceId": "Reference-426",
      "referenceText": "B32<\\BHZ0B<F5L-S\"Z1A6BJNO\\ZXH5LTY/Z[46O$8YR,. 5&[79M1E/GGC;U^(W+BZ5MA\\",
      "referenceOID": "2.7.1.9.5"
    },
    "Reference2": {
      "%seriesCount": "1",
      "referenceId": "Reference-420",
      "referenceText": "E /!QPU)=L&KX9Z*D",
      "referenceOID": "5.9.1.51.0"
    },
    "Reference5": {
      "%seriesCount": "1",
      "referenceId": "Reference-421",
      "referenceText": "7Y=2X(26]@1@V$.XQZ9:,!6PIU?RA\\HGL2';\\J;25X.E:E$638\\]NM([1E\\YQX?+?_I3.8'(&#IK84<_U",
      "referenceOID": "7.1.9.43.17"
    },
    "Reference9": {
      "%seriesCount": "1",
      "referenceId": "Reference-422",
      "referenceText": "XBM+OBE HMAG(>04\\:#=<3Y!I=\\8Y71->A&IH8?O28E3T1C+,%.+Z\"$GCY\"Y;GK$(C$[@-]@&L7X.Y+$SV& UW6AFF>J&S",
      "referenceOID": "5.7.7.9.16"
    }
  }
}

I haven't explored the XDATA mapping associated with %JSON nor investigated the other %JSON classes.

One solution if you were importing the json would be to pre-process the json string and remove the counter appended to the class name but that is a bit cludgy

Nigel

And one more thing, I created the classes as %Persistent because I wanted to see the generated data and because I am referencing the Oid() in the array of Shcema's those classes has to be persistent as well.

Nigel

Hi

I should have included the class definition for Parent

Include DFIInclude Class DFI.Common.JSON.ParentClass Extends (%Persistent, %JSON.Adaptor, %XML.Adaptor, %ZEN.DataModel.Adaptor)
{ Property ParentId As %String(%JSONFIELDNAME = "parentId", %JSONIGNORENULL = 1, %JSONINCLUDE = "INOUT") [ InitialExpression = {"Parent"_$i(^Parent)} ];

Property ParentName As %String(%JSONFIELDNAME = "parentName", %JSONIGNORENULL = 1, %JSONINCLUDE = "INOUT") [ InitialExpression = {..ParentName()} ];

Property Schemas As %ArrayOfObjectsWithClassName(%JSONFIELDNAME = "schemas", %JSONIGNORENULL = 1, %JSONINCLUDE = "INOUT", CLASSNAME = 2, ELEMENTQUALIFIED = 1, REFELEMENTQUALIFIED = 1);

ClassMethod ParentName() As %String
{
quit "Example: "_$i(^Example)
}

ClassMethod BuildData(pCount As %Integer = 1) As %Status
{
set tSC=$$$OK
set array(1)="DFI.Common.JSON.Contact"
set array(2)="DFI.Common.JSON.Patient"
set array(3)="DFI.Common.JSON.Practitioner"
set array(4)="DFI.Common.JSON.Reference"
try {
for i=1:1:pCount {
set obj=##class(DFI.Common.JSON.ParentClass).%New()
set obj.Schemas.ElementType="%Persistent"
set count=$r(12)
for j=1:1:count {
set k=$r(4)+1
set schema=$classmethod(array(k),"%New"),tSC=schema.%Save() quit:'tSC do obj.Schemas.SetObjectAt(schema.%Oid(),$p(array(k),".",4)_"_"_j)
}
quit:'tSC
set tSC=obj.%Save() quit:'tSC
}
}
catch ex {set tSC=ex.AsStatus()}
write !,"Status: "_$s(tSC:"OK",1:$$$GetErrorText(tSC))
quit tSC
}

Nigel

Hi

About a year ago while I was experimenting with IRIS for Health 2019.1 to see what advantages it would give us with the Enterprize Master Patient Index (EMCI) application that HST has been developing. HST had started developing this before IRIS for Health had been released and so they had created FHIR Classes based on the FIR STU3 specification. They created the FHIR classes as %Persistant classes and we use DTL's to convert a FHIR Patient JSON into the HST FHIR Patient class. The one issue we ran into was the Patient's picture which is a Binary Stream. The developer who was writing the UI using Outsystems was using ODBC to retrieve data from the FHIR classes and she was able to specify 'Picture' in her SQL queries and then pass the binary data through some render utility to get it to display correctly on the UI form however there is a restriction in ODBC that the max size for any column is 4000 bytes. In SQL Server the maximum size of a row of data is 8000 bytes and blobs are stored in separate structures from the main table. (Similar to our 'S' global in Cache Default Storage) so though Blobs can be up to 2GB in size you are still restricted if you intend to use ODBC to retrieve or update data in a table.  The ODBC restriction is specific to the version of ODBC. Earlier versions of ODBC had a limit of 2000 bytes. This is irrespective of whether you are working with SQ Server, Oracle or IRIS ODBC drivers. In the documentation I was reading on SQL Server there are performance issues as well and they basically recommend keeping your binary or character stream data in files and they support a couple of techniques that allow their users to execute queries that include BLOB data but the SQL statements are hectic.

Hi

The reason I created this DTL was as follows: I had created an Interface that sent HL7 Messages to an HTTP Operation and provided the message reaches the target server it will respond with an HL7 ACK message (There HL7 HTTP server is working in the equivalent of 'ACK Immediate" mode as opposed to "application" mode. The OnRequest() method in my Business Process calls the HTTP Operation and then calls the FILE Operation. The HTTP Operation will return an HL7 ACK message and I process that in the OnResponse() method of the Business Process. The File Operation writes the HL7 Message, that I sent to the HTTP Operation, to file and by default thats all the File Operation will do but the reason I have the file operation at all is to simulate what should happen when i send the message to HTTP and so I generate an HL7 ACK message to return to the Business Process. That is why I have the DTL to transform the source HL7 Message into a corresponding HL7 ACK Message, and I think that I randomly generate a NACK code, again to be able to test what to do if I were to get an NACK code from the HL7 HTTP Operation. So back in my Business Process OnResponse method I have code to test the response HL7 ACK message and if there is an error I handle it.

With regards the question can it be used for any message structure. Strictly speaking, Yes because the source is an EnsLib.HL7.Message and the response is an EnsLib.HL7.Message and I basically copy the MSH from the source to the target, I swap the Sending and Receiving fields around and I think I generate a new timestamp. The message Control ID remains the same. Any fields that I need to change I pass in using the AUX object. I basically have an AUX class for ever DTL I create when ever I need some runtime value that is not part of the source message in the DTL so the Event Type of the MSH:MessageType is ACK and the Message Structure is just ACK. Then the Code and the Error Text if there is one are assigned in the MSA Segment. I have noticed a mistake in my DTL. When I create the HL7 message that I am sending to the external application the Message Structure is computed based on the Message Type and Trigger Event and I have a lookup table that maps the various Trigger Events to their base Message Structure. For instance an ADT_A08 where the Message Type i ADT and the Trigger Event is A08 then the Base Message Structure for an ADT_A08 is ADT_A01 and I have a method that I call in my business Process that determines the actual message structure from the Message Type and Trigger Event but that is not being called in the DTL so you will see that I am just assigning ACK to the Message structure where the assign should actually read "ACK"_target.{MSH:MessageType.TriggerEvent}

That would give you ACK_A08

Nigel

I think I should have my reply flagged as the accepted answer because I provided a reply that answered the question albeit in a slightly offbeat form but it explained the difference and why you would use $query rather than the other replies that just pointed to documentation. 😉😎👍