New post

Find

Announcement
· Dec 4, 2024

InterSystems Ideas News #17

#InterSystems Ideas Portal

Hi Developers!

Welcome to the 17th edition of the InterSystems Ideas bulletin! This time, you can read about the following:

✓ Bringing Ideas to Reality Contest

✓ Recently posted "Community Opportunity" ideas

✓ Vote for implemented ideas you are curious about

 

  Bring a Community Opportunity or Future Consideration idea to life and join the Bringing Ideas to Reality Contest! Earn exciting prizes and secure your place in the prestigious Hall of Fame on the Ideas Portal.

 Here are several recently posted "Community Opportunity" ideas to help you select the one you'd like to implement for the Development Contest:

Idea Author 
Develop productions using YAML @Yuri Marx
Implement Datadog client that could be easily deployed close to IRIS instance and could be able to send IRIS metrics and logs to Datadog platform (https://www.datadoghq.com). @Mikhail Khomenko
Include an option in HealthShare (UCR) to support natively a vectorized database of patients' clinical data, enabling retrieval-augmented generation (RAG) for communication with market-available large language models (LLMs). @Claudio Devecchi 
Know what IRIS version a class, method or property first appeared in @John Murray
Salesforce Interoperability Adapter @Yuri Marx
IRIS for Health Blockchain connector @Johni Fischer

 Last year, we launched a series of articles showcasing ideas brought to life by community members. We’re excited to continue this series and would love your input on which implemented ideas to feature next. Share your opinion by voting in the poll in this announcement: "Which implemented ideas would you like to know more about?"

👏Thank you all for submitting, voting, commenting and implementing existing ideas.👏
 

Discussion (0)1
Log in or sign up to continue
Question
· Dec 4, 2024

Error importing XSD

#FHIR #XML #Caché #Ensemble #HealthShare

I'm attempting to import all the FHIR XSD files provided by http://hl7.org/fhir but get the immediate and unhelpful error message:

I've tried different versions of EOLs to no avail. Any idea what this error could mean?

Here's the XSD I'm trying to import:

<?xml version="1.0" encoding="UTF-8"?>
<!--
Copyright (c) 2011+, HL7, Inc
 All rights reserved.

 Redistribution and use in source and binary forms, with or without modification, 
 are permitted provided that the following conditions are met:

 * Redistributions of source code must retain the above copyright notice, this 
 list of conditions and the following disclaimer.
 * Redistributions in binary form must reproduce the above copyright notice, 
 this list of conditions and the following disclaimer in the documentation 
 and/or other materials provided with the distribution.
 * Neither the name of HL7 nor the names of its contributors may be used to 
 endorse or promote products derived from this software without specific 
 prior written permission.

 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND 
 ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 
 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. 
 IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, 
 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 
 NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR 
 PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, 
 WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 
 ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 
 POSSIBILITY OF SUCH DAMAGE.

 Generated on Wed, Apr 19, 2017 07:44+1000 for FHIR v3.0.1
-->
<xs:schema xmlns="http://hl7.org/fhir" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://hl7.org/fhir" elementFormDefault="qualified" version="3.0.1">
  <xs:include schemaLocation="account.xsd"/>
  <xs:include schemaLocation="activitydefinition.xsd"/>
  <xs:include schemaLocation="adverseevent.xsd"/>
  <xs:include schemaLocation="allergyintolerance.xsd"/>
  <xs:include schemaLocation="appointment.xsd"/>
  <xs:include schemaLocation="appointmentresponse.xsd"/>
  <xs:include schemaLocation="auditevent.xsd"/>
  <xs:include schemaLocation="basic.xsd"/>
  <xs:include schemaLocation="binary.xsd"/>
  <xs:include schemaLocation="bodysite.xsd"/>
  <xs:include schemaLocation="bundle.xsd"/>
  <xs:include schemaLocation="capabilitystatement.xsd"/>
  <xs:include schemaLocation="careplan.xsd"/>
  <xs:include schemaLocation="careteam.xsd"/>
  <xs:include schemaLocation="chargeitem.xsd"/>
  <xs:include schemaLocation="claim.xsd"/>
  <xs:include schemaLocation="claimresponse.xsd"/>
  <xs:include schemaLocation="clinicalimpression.xsd"/>
  <xs:include schemaLocation="codesystem.xsd"/>
  <xs:include schemaLocation="communication.xsd"/>
  <xs:include schemaLocation="communicationrequest.xsd"/>
  <xs:include schemaLocation="compartmentdefinition.xsd"/>
  <xs:include schemaLocation="composition.xsd"/>
  <xs:include schemaLocation="conceptmap.xsd"/>
  <xs:include schemaLocation="condition.xsd"/>
  <xs:include schemaLocation="consent.xsd"/>
  <xs:include schemaLocation="contract.xsd"/>
  <xs:include schemaLocation="coverage.xsd"/>
  <xs:include schemaLocation="dataelement.xsd"/>
  <xs:include schemaLocation="detectedissue.xsd"/>
  <xs:include schemaLocation="device.xsd"/>
  <xs:include schemaLocation="devicecomponent.xsd"/>
  <xs:include schemaLocation="devicemetric.xsd"/>
  <xs:include schemaLocation="devicerequest.xsd"/>
  <xs:include schemaLocation="deviceusestatement.xsd"/>
  <xs:include schemaLocation="diagnosticreport.xsd"/>
  <xs:include schemaLocation="documentmanifest.xsd"/>
  <xs:include schemaLocation="documentreference.xsd"/>
  <xs:include schemaLocation="eligibilityrequest.xsd"/>
  <xs:include schemaLocation="eligibilityresponse.xsd"/>
  <xs:include schemaLocation="encounter.xsd"/>
  <xs:include schemaLocation="endpoint.xsd"/>
  <xs:include schemaLocation="enrollmentrequest.xsd"/>
  <xs:include schemaLocation="enrollmentresponse.xsd"/>
  <xs:include schemaLocation="episodeofcare.xsd"/>
  <xs:include schemaLocation="expansionprofile.xsd"/>
  <xs:include schemaLocation="explanationofbenefit.xsd"/>
  <xs:include schemaLocation="familymemberhistory.xsd"/>
  <xs:include schemaLocation="flag.xsd"/>
  <xs:include schemaLocation="goal.xsd"/>
  <xs:include schemaLocation="graphdefinition.xsd"/>
  <xs:include schemaLocation="group.xsd"/>
  <xs:include schemaLocation="guidanceresponse.xsd"/>
  <xs:include schemaLocation="healthcareservice.xsd"/>
  <xs:include schemaLocation="imagingmanifest.xsd"/>
  <xs:include schemaLocation="imagingstudy.xsd"/>
  <xs:include schemaLocation="immunization.xsd"/>
  <xs:include schemaLocation="immunizationrecommendation.xsd"/>
  <xs:include schemaLocation="implementationguide.xsd"/>
  <xs:include schemaLocation="library.xsd"/>
  <xs:include schemaLocation="linkage.xsd"/>
  <xs:include schemaLocation="list.xsd"/>
  <xs:include schemaLocation="location.xsd"/>
  <xs:include schemaLocation="measure.xsd"/>
  <xs:include schemaLocation="measurereport.xsd"/>
  <xs:include schemaLocation="media.xsd"/>
  <xs:include schemaLocation="medication.xsd"/>
  <xs:include schemaLocation="medicationadministration.xsd"/>
  <xs:include schemaLocation="medicationdispense.xsd"/>
  <xs:include schemaLocation="medicationrequest.xsd"/>
  <xs:include schemaLocation="medicationstatement.xsd"/>
  <xs:include schemaLocation="messagedefinition.xsd"/>
  <xs:include schemaLocation="messageheader.xsd"/>
  <xs:include schemaLocation="namingsystem.xsd"/>
  <xs:include schemaLocation="nutritionorder.xsd"/>
  <xs:include schemaLocation="observation.xsd"/>
  <xs:include schemaLocation="operationdefinition.xsd"/>
  <xs:include schemaLocation="operationoutcome.xsd"/>
  <xs:include schemaLocation="organization.xsd"/>
  <xs:include schemaLocation="parameters.xsd"/>
  <xs:include schemaLocation="patient.xsd"/>
  <xs:include schemaLocation="paymentnotice.xsd"/>
  <xs:include schemaLocation="paymentreconciliation.xsd"/>
  <xs:include schemaLocation="person.xsd"/>
  <xs:include schemaLocation="plandefinition.xsd"/>
  <xs:include schemaLocation="practitioner.xsd"/>
  <xs:include schemaLocation="practitionerrole.xsd"/>
  <xs:include schemaLocation="procedure.xsd"/>
  <xs:include schemaLocation="procedurerequest.xsd"/>
  <xs:include schemaLocation="processrequest.xsd"/>
  <xs:include schemaLocation="processresponse.xsd"/>
  <xs:include schemaLocation="provenance.xsd"/>
  <xs:include schemaLocation="questionnaire.xsd"/>
  <xs:include schemaLocation="questionnaireresponse.xsd"/>
  <xs:include schemaLocation="referralrequest.xsd"/>
  <xs:include schemaLocation="relatedperson.xsd"/>
  <xs:include schemaLocation="requestgroup.xsd"/>
  <xs:include schemaLocation="researchstudy.xsd"/>
  <xs:include schemaLocation="researchsubject.xsd"/>
  <xs:include schemaLocation="riskassessment.xsd"/>
  <xs:include schemaLocation="schedule.xsd"/>
  <xs:include schemaLocation="searchparameter.xsd"/>
  <xs:include schemaLocation="sequence.xsd"/>
  <xs:include schemaLocation="servicedefinition.xsd"/>
  <xs:include schemaLocation="slot.xsd"/>
  <xs:include schemaLocation="specimen.xsd"/>
  <xs:include schemaLocation="structuredefinition.xsd"/>
  <xs:include schemaLocation="structuremap.xsd"/>
  <xs:include schemaLocation="subscription.xsd"/>
  <xs:include schemaLocation="substance.xsd"/>
  <xs:include schemaLocation="supplydelivery.xsd"/>
  <xs:include schemaLocation="supplyrequest.xsd"/>
  <xs:include schemaLocation="task.xsd"/>
  <xs:include schemaLocation="testreport.xsd"/>
  <xs:include schemaLocation="testscript.xsd"/>
  <xs:include schemaLocation="valueset.xsd"/>
  <xs:include schemaLocation="visionprescription.xsd"/>

</xs:schema>

Discussion (0)1
Log in or sign up to continue
Digest
· Dec 4, 2024

Internal Tech Article Contest: Be Part of It!

#Digest #Developer Community Official

Dear colleague,

Let us remind you that you still have time to participate (and maybe win) in the Internal Technical Article Writing Contest:

✍️ Tech Article Writing Contest for InterSystems Employees ✍️

Write an article on any topic related to InterSystems products or services and publish it on the Developer Community by December 15, 2024.

🎁 Gifts for everyone: A special gift for each author who takes part in the competition!

🏅 Prizes for the best articles!

Important Dates:

  • December 15, 11:59 pm EDT: Deadline for submissions.
  • December 16 - 22: Voting period. 

➡️ All details can be found in this Insider Article.

Article
· Dec 4, 2024 2m read

HL7 -> SDA -> FHIR -> Crecimiento Personal

#FHIR #InterSystems IRIS

Tengo un gran árbol fuera de mi ventana. Aquí en Phoenix, Arizona, EE. UU., todavía hace calor y está soleado, así que nuestras plantas siguen cubiertas de frondosa vegetación, a pesar de que en muchos otros lugares ya están en pleno otoño. Mi escritorio está orientado de tal manera que puedo ver el árbol durante todo el día. Parte de la razón por la que me gusta tener el escritorio frente al árbol es porque necesito un descanso de mirar las pantallas de la computadora, pero la otra razón es porque de vez en cuando necesito recordatorios de la naturaleza. Hoy me recuerda dos cosas:

  1. El crecimiento requiere absorber del entorno.
  2. El crecimiento no siempre ocurre en la dirección que esperáis.

Para el reciente Desafío de Videos Tecnológicos de InterSystems, preparé una presentación que resumía cómo configurar la conversión de un mensaje HL7 personalizado a SDA y luego enviarlo a un endpoint de un servidor FHIR para convertirlo en JSON FHIR. Para ello, realmente tuve que aventurarme en un territorio nuevo para absorber toda la información necesaria, y terminé desarrollando habilidades que no esperaba.

Al igual que el árbol cuenta con nutrientes abundantes a su alrededor, nosotros tenemos a nuestra disposición mucha documentación que detalla los pasos necesarios para configurar nuestras producciones, servidores, etc., pero a menudo están en lugares tan dispersos que reunirla toda y darle cohesión puede ser un verdadero desafío. Esta fue la motivación detrás de mi video. Quería demostrar cómo recopilar esa información de manera que alguien pudiera seguir los pasos de forma razonable e idealmente mejorarlos.

En el proceso, obtuve una mejor comprensión de las configuraciones de producción y tuve la oportunidad de interactuar con herramientas de InterSystems que antes no había explorado (como el RecordMapper, el Servidor FHIR, etc.). Aún quedan muchas cosas por explorar y experimentar, pero cada ramita se convierte en rama con el tiempo, y este es el comienzo de un nuevo conjunto de habilidades.

Como complemento a la presentación en video, me gustaría ofreceros un refugio a la sombra en forma de resumen de los pasos que seguí para construir mi solución, con enlaces a las secciones correspondientes del video:

  1. Configurar vuestro endpoint del servidor FHIR
  2. Crear un mapeo de registros utilizando vuestros datos de muestra
  3. Configurar vuestra transformación de datos personalizada
  4. Construir vuestros componentes de producción
  5. Configurar vuestros componentes de producción

Aunque espero que esto os sea útil, sé que todavía tengo mucho por crecer. Espero que todos podamos seguir ayudándonos y apoyándonos mutuamente.

Discussion (0)1
Log in or sign up to continue
Question
· Dec 4, 2024

[InterSystems IRIS JDBC] Communication link failure: License Violation

#InterSystems IRIS

使用dbeaver 连接数据库, 弹出[InterSystems IRIS JDBC] Communication link failure: License Violation错误.

Discussion (0)1
Log in or sign up to continue