User bio
404 bio not found
Member since Nov 10, 2015
Posts:
Replies:
Right. But we should have a quicker way to get the parameter in our Python code.
Replacing
set r = ..#MYPARAM
with
r = iris.cls('MyPackage.Subpackage.ClassName')._GetParameter('MYPARAM')
doesn't seem too "developer friendly" to me
By the way, it varies if we're in a ClassMethod or in an instance Method. In instance we could do:
r = self._GetParameter('MYPARAM')
which it's more acceptable...
But, in a classmethod it seems that our only chance would be the long version.
I wonder if we could translate them to Python as read-only special properties, adopting perhaps some convention in their name to avoid the conflicts in the (unusual) case that there is a parameter with same name that a property.
I think they do so in Windows 11 :-)
Open Exchange applications:
Followers:
Following:
Global Masters badges:







Thinking in how our intellisense works, we need classes generated... thinking on how FHIR work, we will need to use non-persistent objects but with features like the ones that inherite from %Dynamic*** or the ones that make use of %JSON.Adapter... so one (very general) idea would be to start from the JSON schema of a FHIR release or profile with which you need to work and have a tool that automatically generates the classes that map such schema... and those classes have to have the easiness to export/import JSON documents that %Dynamic* and %JSON.* packages give us.
We should have in mind that these are intermediary packages, no need to persist, we just need them to help us for having intellisense when manual programming FHIR resources, also to help in DTL definitions, etc... so we could have several packages, one for each FHIR release/profile we want to use: r4.*, r4uscore.*, r5il.*,... in the end the objects instanced will inherit for a common class of type %<SomeKindOfNew>DynamicObject.... that provide the helpful logic to use %ToJSON, %FromJSON, %BulkExport,... and to be used in DTL definitions from HL7 to r4.* resource... DTL from r4.* to r5.* resources,... and the capability to be easily serializable or work as virtual document if needed to be sent within our interoperability framework...
Just thinking aloud