Hi,
We have some concerns on how to implement FHIR, do we do facade?, how do we get resources?, what is a resource?, is a resource "Patient" or an instance of a patient?, How can we have a FHIR repository AND send the patient details to healthshare MPI?
Has anyone correctly created a FHIR server that has custom methods?, handles "normal" methods and forwards onto Healthshare MPI , processing the response and creates a accurate FHIR response back to the calling system.
How do you assign a property in a RUL (not a DTL or BPL) from a function value? I've tried with the package/classname, without, with .., without and even looked all the way down to the parser but still can't see how. There is no examples and the documentation doesn't help
So this works
<assign property="RuleActionUserData" value=""A01""></assign>
This doesn't complile
<assign property="RuleActionUserData" value="##class(SomePackage.SomeClass).EventTypeToHL7Type(Document)"></assign>
SomePackage.SomeClass extends EnsRules and the method is a classmethod and final
Hello All,
I have used github (outside of IRIS) for many many years and have no problem with it. Also used SVN and other source control systems.
I have a conceptual problem understanding the ISC github links and how they work via VSCode.
https://github.com/intersystems/git-source-control
Our server is on Linux.
What I've done:
1. On Linux Server - d ##class(SourceControl.Git.API).Configure()
2. Create a local repo (we have a local git), say https://repo/myrepo
3. VSCode installed Object script addons, github Pull requests extension
4. VSCode Connect to namespace on server, all good
I have the unfortunate job of installing IRIS and Healthshare (real Healthshare not Healthconnect) on 16 difference instances (tst, stg, prd with mirrors etc). the Dev was set up manually (mostly by me).
So I decided to create a class that installed the db's, namespaces, mappings and HSREGISTRY options , i then decided an installer manifest was a better idea, I keep changing my mind on which!. I understanding manifest is "typically" for dockers to create the environment but have seen ISC use them for creating new setups aswell (outside docker)