发布新帖

查找

InterSystems 官方
· 三月 21, 2023

Announcing developer preview #4 for InterSystems IRIS, IRIS for Health, & HealthShare Health Connect 2023.1

InterSystems announces its fourth developer preview, as part of the developer preview program for the 2023.1 release. Many updates and enhancements have been added in 2023.1 and there are also brand-new capabilities, such as production-ready support for Columnar Storage, ability to use Bulk FHIR, and support to MacOS 13 Ventura. Additionally, a new feature to provide the ability to use Foreign Tables is being released as "experimental" and will be accessible through an Early Access Program (EAP). Some of these features or improvements may not be available in this current developer preview.

Future preview releases are expected to be updated biweekly and we will add features as they are ready. Please share your feedback through the Developer Community so we can build a better product together.

Documentation can be found at these links below. They will be updated over the next few weeks until launch is officially announced (General Availability - GA):

In addition, check out this link for upgrade information related to this release.

As usual, Extended Maintenance (EM) releases come with classic installation packages for all supported platforms, as well as container images in Docker container format.  For a complete list, refer to the Supported Platforms document.

Installation packages and preview keys are available from the WRC's preview download site or through the evaluation services website (use the flag "Show Preview Software" to get access to the 2023.1).

Container images for both Enterprise and Community Editions of InterSystems IRIS and IRIS for Health and all corresponding components are available from the new InterSystems Container Registry web interface. For additional information about docker commands, please see this post: Announcing the InterSystems Container Registry web user interface.

The build number for this developer preview release is 2023.1.0.218.0.

For a full list of the available images, please refer to the ICR documentation. Alternatively, tarball versions of all container images are available via the WRC's preview download site.

讨论 (0)1
登录或注册以继续
请注意,此帖子已过时。
公告
· 三月 20, 2023

Sneak Peek (at least for this week)

 Hi Community:

As you may know, I am the person who does the program and scheduling for our Global Summit sessions, so I can give you a sneak peek at our agenda before it is published.

I'm happy to report that we will have two special, four-hour workshops on Sunday, June 4, which is the day you arrive to register in Hollywood, Florida.

One is the return of the standing-room only 2022 workshop with our FHIR guru, Russ Leftwich - "Getting to Know FHIR: The Best Explanation of FHIR They've Ever Heard." Needless to say, we've reserved a bigger room.

Plus, we are planning eight related breakout sessions:

  1. "FHIR to IntegratedML: Can You Get There from Here?'
  2. "Building a FHIR Façade" 
  3. "How to Customize Your FHIR Server"
  4. "Clinical Alerts and Notifications on FHIR: Putting the Healthcare Action Engine into the Workflow"
  5. "Performing Advanced FHIR Validation"
  6. "Clinical Research Data Pipeline using FHIR and OMOP"
  7. "FHIR in the Cloud"
  8. "Introducing Bulk FHIR Export"

Our second workshop in an introduction to containers -- "Working with Containers and InterSystems Technology" - led by Derek Robinson from our online learning team. It will prepare you for these two related sessions

  1. "The Container Lifecycle: When is Your App Ready to Accept Work?"
  2. "Can you Autoscale This?  Lessons from the Field on Kubernetes"

Register TODAY for Global Summit 2023 to take advantage of Early Bird Prices. (You will be able to register for sessions, including the workshops, soon.)

讨论 (0)1
登录或注册以继续
问题
· 三月 15, 2023

How to convert a FHIR Patient resource in XML format into a Cache object

Hi.

We are going to have basic patient demographic data coming in to Cache via a webservice. I thought that I should define the input as XML something like the FHIR format (with UK extensions).

In the past we've input XML streams and used the  %XML.Reader to convert them to matching classes successfully, so I thought it would be easy. However, I've found that the FHIR format stores everything in attributes like:

  <gender value="male"/>
  <birthDate value="1982-01-23"/>

Looking in the Cache documentation here there seems no easy way to make a property match to an attribute of "value" without defining another class for each item with a single property called "value" and  XMLPROJECTION = "ATTRIBUTE" . Is that correct or have I missed something? I could invest in Ensemble or IRIS (though I can see nothing different in the IRIS documentation), but seems overkill for one small inbound message. Or should I forget FHIR and stick to a simple XML structure.

Thanks / Mike

6 Comments
讨论 (6)2
登录或注册以继续
问题
· 三月 14, 2023

Creating Http Responses

Hello,

I want to generate and return an http response based on the input of a http GET request. For my first steps I used an EnsLib.Http.GenericService, which uses an EnsLib.HTTP.InboundAdapter to receive requests like http://[my server]:[my-port]/some-path?ID=12345678.

On the inbound side I receive a EnsLib.HTTP.GenericMessage Object which contains the parameters and some other useful information that I can work with. What I would like to do now is to create a simple HTML page, which contains some Information specific for the given parameter values. All my different attempts to return something, which can be parsed by a browser (or at least shown as a http response in postman) failed up to now.

I think this task is normally done by a webapp, but using an interoperability production makes other things a lot easier for me.

Could anyone provide a snippet how to create a valid Response object inside the OnRequest method of an Ens.BusinessProcess to make me understand the priciple? The target is to receive the request from any web browser and return a page, which then is shown inside of the browser as the result of the request.

Thanks and regards,

Martin

5 Comments
讨论 (5)1
登录或注册以继续
文章
· 三月 12, 2023 阅读大约需 1 分钟

Create FHIR REST Client

Add a credential to login the FHIR REST interface - in this case only consider a basic authentication

 

 

Add Service Registry  - in this case only consider a basic authentication

- setup a HTTP service

- input the Path to the FHIR Server

- input the URL to the FHIR service

- use the credential profiled
 

 

Add a "HS.FHIRServer.Interop.HTTPOperation"

Choose the Service Name

 

Test the FHIR Client

 

Trace the test result

6 Comments
讨论 (6)4
登录或注册以继续