Find

InterSystems Official
· Aug 7, 2024

IAM 2.8.4.11 & 3.4.3.11 リリースのお知らせ

#InterSystems API Manager (IAM) #Release #InterSystems IRIS #InterSystems Official

InterSystems API Manager (IAM) のバージョン 2.8.4.11 & 3.4.3.11 が公開されました。 これらは、長期的にサポートされている IAM の 2 つのバージョンの最新版です。これらのリリースには重要な修正が含まれており、すべてのお客様にアップグレードをお勧めします。

IAM 3.0または3.2をお使いのお客様は、これらのバージョンのサポートがまもなく終了するため、3.4.3.11にアップグレードすることをお勧めします。

IAM は、InterSystems IRIS サーバとアプリケーション間の API ゲートウェイであり、HTTP ベースのトラフィックを効果的に監視、制御、管理するためのツールを提供します。IAM は、InterSystems IRIS ライセンスの無償アドオンとして利用できます。

IAMは、WRCソフトウェア配布サイトのComponentsエリアからダウンロードできます。

 IAM のダウンロード、インストール、使用開始方法については、 インストール・ガイド を参照してください 。InterSystems IRIS での使用に関する詳細な情報については IAM Version 3.4 Guide を参照してください。パートナーであるKong社では、Kong Gateway (Enterprise) 3.4 ドキュメント にて、 IAM の使用に関する詳細なドキュメントを提供しています。

IAMは、OCI（Open Container Initiative）、別名Dockerコンテナ形式でのみ利用可能です。コンテナイメージは、Linux x86-64およびLinux ARM64用のOCI準拠のランタイムエンジンとして利用可能です。詳細は、サポート対象プラットフォームドキュメント をご覧ください。

Discussion (0)0
Log in or sign up to continue
Article
· Aug 7, 2024 1m read

第三章 控制 xsi type 属性的使用

#InterSystems IRIS

第三章 控制 xsi:type 属性的使用

控制 xsi:type 属性的使用

默认情况下， SOAP 消息仅包含顶级类型的 xsi:type属性。例如：

<?xml version="1.0" encoding="UTF-8" ?>
...
<types:GetPersonResponse>
<GetPersonResult href="#id1" />
</types:GetPersonResponse>
<types:Person id="id1" xsi:type="types:Person">
<Name>Yeats,Clint C.</Name>
<DOB>1944-12-04</DOB>
</types:Person>  
...

在这些示例中，已添加换行符以提高可读性。要将此属性用于 SOAP 消息中的所有类型，请执行以下操作之一：

Discussion (0)1
Log in or sign up to continue
Announcement
· Aug 7, 2024

InterSystems Certification is looking for question writers for our upcoming InterSystems TrakCare Integration exam

#Certification #TrakCare

The InterSystems Certification Team is building an InterSystems TrakCare Integration certification exam and is looking for Subject Matter Experts (SMEs) from our community to help write and review questions. You, as a valued InterSystems community member, know the challenges of working with our technology and what it takes to be successful at your job. A work assignment will typically involve writing 15 assigned questions and reviewing 15 assigned directly to you.  

Proposed Project Work Dates: The work assignments will be assigned by the Certification Team through September 15, 2024. 

Here are the details: 

Action Item 

Details 

Contact InterSystems Certification 

Write to certification@intersystems.com to express your interest in the Certification Subject Matter Expert Program. Tell us that you are interested in being an InterSystems TrakCare Integration SME (an individual with at least one year of experience with InterSystems TrakCare Integration tasks). 

Complete project profile - External Participants 

If you are an external volunteer looking to participate, a team member will send you a profile form to determine if your areas of expertise align with open project.  

Accept 

If you are selected for an exam development opportunity, a team member will email you a Non-Disclosure Agreement requiring your signature. 

Train 

After receiving your signed document, and before beginning to write questions, you will be asked to watch a short training video on question-item writing. 

Participate 

Once onboarded, the Certification Team will send you information regarding your first assignment. This will include: 

  • an invitation to join Certiverse, our new test delivery platform, as an item writer and reviewer 
  • an item writing assignment, which usually consists of the submission of 15 scenario-based questions 
  • an alpha testing assignment, which usually consists of reviewing 15 items written by your peers 

You will typically be given one month to complete the assignment. 

Subject Matter Experts are eligible for a SME badge based on successful completion of their exam development participation. SMEs are also awarded the InterSystems TrakCare Integration certification if they write questions for all KSA Groups and their questions are accepted

Interested in participating? Email certification@intersystems.com now! 

KSA Group 

KSA 

Target Item 
  1. Demonstrates mastery of foundational concepts required for TrakCare integrations 

1. Accesses TrakCare system and locates test patients and data 
  1. Describes components on the EPR 
  1. Explains how Edition provides region-specific functionality 
  1. Uses TrakCare to perform patient and episode lookup, and to perform other basic operations 

 

2. Examines and configures basic TrakCare settings 
  1. Describes important items in the Configuration Manager (e.g. Site Code, System Paths, etc.) 
  1. Identifies steps to configure integration-related code tables 
  1. Toggles TrakCare features 

 

3. Examines and interprets TrakCare data model and data definitions, and performs basic SQL queries 
  1. Examines and interprets data definitions and relationships between tables using TrakCare Data Dictionary UI 
  1. Examines and interprets data definitions, relationships, and global storages with InterSystems class reference function 
  1. Performs basic SQL queries on patient, episode, and order items 

 

4. Examines and interprets integration security configuration settings 
  1. Describes TrakCare application security model 
  1. Examines security settings using the Management Portal in InterSystems IRIS 

 

5. Interprets HL7 V2 requirements 
  1. Describes common HL7 V2 message types (e.g., ADT, SIU, REF, and ORM/ORU) 
  1. Correlates TrakCare triggering events with HL7 V2 message types 
  1. Describes mapping between HL7 V2 data and TrakCare data model 

 

6. Interprets HL7 FHIR requirements 
  1. Names common HL7 FHIR resources 
  1. Correlates HL7 FHIR resources with TrakCare data model 

 

7. Identifies elements in an SDA 
  1. Identifies important elements within SDA structure 
  1. Examines SDA definition by using the InterSystems class reference guide 
  1. Correlates SDA elements with HL7 V2 message segments and fields  

2. Uses the HealthCare Messaging Framework (HMF) for TrakCare integrations 

1. Demonstrates mastery of foundational HMF concepts 
  1. Uses the HMF (TrakCare/SDA3) Clinical Summary 
  1. Uses the HMF External Search and Merge workflow 
  1. Uses the HMF FHIR Manager 

 

2. Designs and configures HMF productions 
  1. Identifies steps to define and configure HMF according to the integration solution design/architecture 
  1. Examines existing HMF configuration settings 
  1. Lists roles of each generated production (System, Router, Gateway) 
  1. Prepares HMF productions and interfaces according to the integration solution design 

 

3. Develops and customizes HMF productions 
  1. Formulates development and customization plans 
  1. Develops custom inbound/outbound methods 
  1. Enhances generated DTL code 
  1. Creates extensions 
  1. Enables/disables Event Triggers/productions using Integration Manager 
  1. Configures Outbound Query interfaces and makes process calls to search patient information from an external system. 
  1. Creates additional SDA elements (extensions) at container and patient levels 

 

4. Deploys HMF solutions 
  1. Prepares HMF adapter-based productions and interfaces 
  1. Contrasts local versus remote deployments 

 

5. Manages and monitors HMF productions 
  1. Examines integration events and SDA content using Integration History UI 
  1. Views configuration settings (e.g., ports, URLs, file paths, etc.) for business services and business processes generated in each production (System, Router, and Gateway) 
  1. Identifies production status using the Production Manager and InterSystems IRIS Message Viewer 
  1. Examines message workflow using Visual Trace in the InterSystems IRIS Management Portal for each production 

 

6. Troubleshoots HMF productions 
  1. Examines and interprets low-level HMF trace details in ^zTRAK("HMF") global 
  1. Examines HMF production settings 
  1. Formulates resolution strategies 

3. Configures TrakCare for external access and access to 3rd party applications 

1. Configures inbound data access 
  1. Uses external SQL tools (e.g., WinSQL to perform SQL queries) 

 

2. Configures outbound data access 
  1. Creates and runs SQL queries against external tables or views 

 

3. Uses SOAP web services 
  1. Writes InterSystems ObjectScript code to invoke external SOAP web services 
  1. Uses SOAP Wizard to create proxy clients 
  1. Uses industry-standard tools such as SoapUI, Postman, and CURL to make SOAP calls to TrakCare 

 

4. Links to External Viewer 
  1. Configures External Viewer for TrakCare to launch into external PACS 
  1. Associates External Viewer to receiving location 

 

5. Launches into 3rd party application with context 
  1. Names TrakCare in-process variables 
  1. Creates and configures custom charts 

 

6. Uses TrakCare REST APIs 
  1. Retrieves TrakCare API Swagger documentation 
  1. Configures TrakCare REST APIs using the API Manager 
  1. Audits REST API history 
Discussion (0)1
Log in or sign up to continue
Question
· Aug 7, 2024

DateTimeDifference in seconds

#Ensemble

Hi All ,

I have a dateTime in the format = "2024-08-07 17:58:51.563"
I need the difference between current date time and above one 
I need it in seconds.

5 Comments
Discussion (5)2
Log in or sign up to continue
Announcement
· Aug 7, 2024

Do you use client-side editing in VS Code? If so, we want your feedback!

#Development Environment #Git #Open Source #Source Control #Tools #VSCode #InterSystems IRIS #InterSystems IRIS for Health

The VS Code extension development team is looking for beta testers to provide feedback on a proposed overhaul of the client-side editing workflow. The full list of changes can be found in the GitHub pull request description. Here are the highlights:

  • Support the use of client-side editing in any non-isfs workspace folder, not just folders in your local file system. For example, with VS Code Remote Development.
  • Create an index of all Classes, MAC and INT routines, and Include files inside non-isfs workspace folders. This will be used to determine the URI of classes and routines (for example, for Go To Definition).
  • Automatically sync all file changes, creations and deletions in client-side workspace folders with the connected server. This can be turned off using the new objectscript.syncLocalChanges setting. This new setting replaces the old objectscript.importOnSave setting, which is no longer needed. If objectscript.importOnSave was set to false, the extension will set objectscript.syncLocalChanges to false upon activation so no user migration is required.
  • Automatically show and hide the InterSystems Explorer and Projects Explorer views based on the folders in the workspace. InterSystems Explorer is only shown if there is at least one non-isfs workspace folder. Projects Explorer is only shown if there is at least one isfs folder. This replaces the objectscript.showExplorer setting.
  • Change the default value of the objectscript.explorer.alwaysShowServerCopy setting to true. The InterSystems Explorer should always show the server copy since the local copy can be opened from the files explorer.
  • Change the default value of the objectscript.autoAdjustName setting to false. Now that we have an index of the workspace, we no longer require that a document's name match the file path for the extensions to find it.
  • Cache the list of Studio Abstract Document extensions that are supported for each server connection so we can properly import them from client-side folders. Importing abstract documents is now independent of the objectscript.export settings, except for DFI’s which still check the export settings to preserve the current path-splitting behavior. Any file within a workspace folder that has a supported abstract document extension will be imported with the last part of the path used as the server name (except for DFI’s that match the export settings). For example, if the file path on disk is /src/other/example.ext, the server name will be example.ext.

In addition to general feedback on the changes, there are four design questions that have yet to be answered:

  1. Do any users want the InterSystems Explorer (NOT the default VS Code file explorer) to show the local copies of the documents? If not, the objectscript.explorer.alwaysShowServerCopy setting can be removed. EDIT: This setting will be retained for backwards compatibility.
  2. Do any users edit DFI files locally and have repositories that depend on the folder splitting behavior? If not, that special handling will be removed and DFIs will be treated like any other Abstract Document type. EDIT: This behavior will be retained for backwards compatibility, but newly exported DFI files will not be split into subfolders.
  3. Should the automatic deletion of files on the server when the local copy is deleted be guarded by a setting so users can disable it? EDIT: This is covered by the new objectscript.syncLocalChanges setting.
  4. This extension has a feature that will attempt to adjust the name of a class or routine when it's copied or moved to a new location within the workspace folder. This was implemented to help developers keep the file path and document name in sync. It can be turned off using the objectscript.autoAdjustName setting. Do users value this feature? Should the objectscript.autoAdjustName setting be set to false by default? Should this feature be removed entirely since the document index removes the need for the path to match the document name? EDIT: This setting's default has been changed to false.

Here's how you can share your feedback:

  1. Download the zip file at the end of this post and extract the vsix file contained within.
  2. Install the vsix file in VS Code using these directions, or by dragging the file from your file explorer into the Extensions view in VS Code.
  3. Follow your normal development workflow and try out some new features.
  4. Share your experience here, or on the GitHub pull request.

Thanks in advance for trying this out and we hope you like the changes!

vscode-objectscript-2.12.11-dev.1401.vsix.zip

35 Comments
Discussion (35)10
Log in or sign up to continue