新しい投稿

検索

お知らせ
· 2024年12月23日

Winners of the InterSystems "Bringing Ideas to Reality" Contest

Hi Community,

It's time to announce the winners of the "Bringing Ideas to Reality" Contest

Thanks to all our amazing participants who submitted 13 applications 🔥 

Now it's time to announce the winners!

Experts Nomination

🥇 1st place and $5,000 go to the vault-link app by @Henrique Dias, @Henry Pereira, @José Pereira 

🥈 2nd and 3rd place and $2,250 each go to the IRIS Global VSCode Editor app by @Yuri Marx and tz - ObjectScript Time Zone Conversion Library app by @Eric Fortenberry 

🏅 4th place and $750 go to the docs-intersystems app by @Dmitry Maslennikov 

🏅 5th place and $500 go to the iris-unit-test-dashboard app by @Chi Nguyen-Rettig 

🌟 $100 go to the iris-HL7v2Gen app by @Muhammad Waseem

🌟 $100 go to the iris-http-calls app by @Oliver Wilms 

🌟 $100 go to the SharePoint Online SPO REST API app by @Mark OReilly 

🌟 $100 go to the Doxygenerate app by @John Murray 

🌟 $100 go to the ks-fhir-gen app by @Robert Barbiaux 

Community Nomination

🥇 1st place and $1,000 go to the  Database-Size-Monitoring app by @sara aplin 

🥈 2nd place and $750 go to the ServiceInspection app by @Wolis Oliavr

🥉 3rd place and $500 go to the IRIS Global VSCode Editor app by @Yuri Marx 

🏅 4th place and $300 go to the vault-link app by @Henrique Dias, @Henry Pereira, @José Pereira 

🏅 5th place and $200 go to the iris-unit-test-dashboard app by @Chi Nguyen-Rettig

Our sincerest congratulations to all the participants and winners!

Join the fun next time ;)

6 Comments
ディスカッション (6)3
続けるにはログインするか新規登録を行ってください
質問
· 2024年12月23日

Webterminal pagination from command ^%G does not work

Hello,

It looks like command D ^%G from webterminal does not respect parameter "Screen size for paging"

In this example it should show only 2 results and ask for more, as it does in a pure terminal session

From webterminal

SQX > D ^%G
Device: 
Right margin: 80 => 
Screen size for paging (0=nopaging)? 24 => 3
For help on global specifications DO HELP^%G
Global ^["TAB"]TBS("URGZN",)
^TBS("URGZN","AMB")="A#Ambulatori#01"
             "BOX")="A#Boxos#01"
             "CHB")="A#Càmara Hiperbàrica#01"
             "COR")="P#COR"
             "ESP")="P#ESP"
             "OBP")="P#OBP"
             "OBS")="A#Observació#01"
             "PAS")="P#PAS"
             "PED")="A#Pediatria#06"
             "RAP")="P#RAP"
             "SEE")="A#SEE#01"
             "SLP")="A#Sala parts#04"
             "SLS")="A#Sala sillons#01"

From terminal

SQX>D ^%G

Device:
Right margin: 80 =>
Screen size for paging (0=nopaging)? 24 => 3
For help on global specifications DO HELP^%G
Global ^["TAB"]TBS("URGZN",)
^TBS("URGZN","AMB")="A#Ambulatori#01"
             "BOX")="A#Boxos#01"
(M)ore, (L)ine, (S)croll, (Q)uit? M =>

ディスカッション (0)1
続けるにはログインするか新規登録を行ってください
ダイジェスト
· 2024年12月23日

Publications des développeurs d'InterSystems, semaine Décembre 16 - 22, 2024, Résumé

Articles
#Portail d'apprentissage
Annonces
#InterSystems IRIS
Publication de l'IPM 0.9.0
Par Sylvain Guilbaud
#Autre
#Communauté des développeurs officielle
Décembre 16 - 22, 2024Week at a GlanceInterSystems Developer Community
質問
· 2024年12月23日

Interfaz sencilla para modificar y reenviar mensajes HL7

Hola a todos,

Estoy buscando alguna herramienta que se pueda utilizar como base para crear una interfaz que permita a un usuario no técnico reenviar mensajes de manera sencilla. La idea es que el usuario pueda encontrar un mensaje HL7 ya enviado y reenviarlo modificando campos específicos del mensaje sin necesidad de tener ningún conocimiento técnico.

Un ejemplo sería algo similar al buscador de Ensemble, pero con un enfoque menos técnico y mucho más intuitivo y que solo permita cambiar 1 o 2 campos. ¿Existe alguna solución en la comunidad o algo que pueda adaptar para este propósito? Algo tipo frontend en React que se comunique con backend IRIS para el reenvio. No encuentro nada y igual se ha de crear ya desde cero, pero por si acaso...

Gracias de antemano por vuestra ayuda.

2 Comments
ディスカッション (2)2
続けるにはログインするか新規登録を行ってください
質問
· 2024年12月23日

Import error when using SOAP wizard with Gematik TI Connector WSDL Files

Hello Community,

I'm trying to import WSDL service descriptions from Gematik (https://www.gematik.de/) to allow communication with the german TI infrastructure using the TI connectors webservice interface over a IRIS healthconnect SOAP operation. For import I'm using the SOAP Wizard Add-Inn from Studio.

The WSDL files can be found here: https://fachportal.gematik.de/fileadmin/Fachportal/Downloadcenter/Schemata-_und_WSDL-Dateien/Schema-_und_WSDL-Dateien/OPB3.1_Schemadateien_R3.1.2_Kon_PTV3_20191002.zip

The interface specification and some helpful graphics are published here: https://gemspec.gematik.de/downloads/gemILF/gemILF_PS/gemILF_PS_V2.22.0.html

I exctracted the folder with the schema files to the filesystem of our Health Connect server and tried to import some services.

CardService and EventService worked as expected without any problems. With some configuration of the connectors endpoint it is possible to list all card terminals associated with the specific connector. When importing the VSDService, which allows to read health ensurance card data from card reader terminals, I got import errors. The file is located in conn/vsds/VSDService.wsdl relatively located to the root folder of the archive. The file could be loaded and parsed in the first place, but when trying to create class files an business operations I got an error

I thought it might be a rights problem and changed ownership of all files to the cacheusr (called irisuser in new installations), but this did not change anything.

I found this post in the developer community, but this one also does not seem to cover my case. The VSDService.wsdl is parsable and the error occurres at a later point while processing the contents. I had a similar error before with another file, when trying to import without providing the complete folder structure and contained files. In the current case all references exist and should be resolvable. Here is the WSDL File I'm trying to import:

<?xml version="1.0" encoding="UTF-8"?>
<!-- gematik revision="\main\rel_online\rel_ors1\1" -->
<!-- edited with XMLSpy v2010 (http://www.altova.com) by n.n. (gematik) -->
<definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:GERROR="http://ws.gematik.de/tel/error/v2.0" xmlns:VSD="http://ws.gematik.de/conn/vsds/VSDService/v5.2" name="VSD" targetNamespace="http://ws.gematik.de/conn/vsds/VSDService/v5.2">
	<documentation>
		Copyright (c) 2011, gematik - Gesellschaft für Telematikanwendungen der Gesundheitskarte mbH. Alle Rechte vorbehalten.
		Beschreibung: Dienste zum Lesen der Versichertenstammten von einer eGK
	</documentation>
	<types>
		<xs:schema>
			<xs:import schemaLocation="VSDService.xsd" namespace="http://ws.gematik.de/conn/vsds/VSDService/v5.2"/>
			<xs:import schemaLocation="../../tel/error/TelematikError.xsd" namespace="http://ws.gematik.de/tel/error/v2.0"/>
		</xs:schema>
	</types>
	<message name="ReadVSDRequestMessage">
		<part name="parameter" element="VSD:ReadVSD"/>
	</message>
	<message name="ReadVSDResponseMessage">
		<part name="parameter" element="VSD:ReadVSDResponse"/>
	</message>
	<message name="FaultMessage">
		<part name="parameter" element="GERROR:Error"/>
	</message>
	<portType name="VSDServicePortType">
		<operation name="ReadVSD">
			<input message="VSD:ReadVSDRequestMessage"/>
			<output message="VSD:ReadVSDResponseMessage"/>
			<fault name="FaultMessage" message="VSD:FaultMessage"/>
		</operation>
	</portType>
	<binding name="VSDServiceBinding" type="VSD:VSDServicePortType">
		<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
		<operation name="ReadVSD">
			<soap:operation soapAction="http://ws.gematik.de/conn/vsds/VSDService/v6.0#ReadVSD"/>
			<input>
				<soap:body use="literal"/>
			</input>
			<output>
				<soap:body use="literal"/>
			</output>
			<fault name="FaultMessage">
				<soap:fault name="FaultMessage" use="literal"/>
			</fault>
		</operation>
	</binding>
	<service name="VSDService">
		<port name="VSDServicePort" binding="VSD:VSDServiceBinding">
			<soap:address location="http://unspecified"/>
		</port>
	</service>
</definitions>

I would really appreciate, if anyone would help me out with some ideas how to fix this error.

Kind regards,

Martin

5 Comments
ディスカッション (5)1
続けるにはログインするか新規登録を行ってください