Nova postagem

Pesquisar

Anúncio
· jan 30

Agenda de l'InterSystems France & Benelux Ready 2026

#Summit

Bonjour à tous,

Je suis heureux de vous présenter le programme de Ready 2026.

InterSystems France & Benelux READY 2026 Agenda

Jour 1 – Séances plénières et thématiques

Matin : Séances d’ouverture et plénières
Après-midi : Séances axées sur la santé | Séances axées sur les plateformes de données

Jour 2 – Ateliers et échanges technologiques

Matin : Séances FHIR | Séances HealthShare | Plateforme de données | Journée des utilisateurs TrakCare
Après-midi : Échanges technologiques | Séances pour la communauté des développeurs | Groupes de travail | Pavillon des startups et des partenaires | Journée des utilisateurs TrakCare

L'agenda complet est disponible ici.

Nous avons hâte de vous voir au Ready 2026!

Discussão (0)1
Entre ou crie uma conta para continuar
Pergunta
· jan 30

Electric Dirt Bike Buying Guide in Australia for Smart Riders

#Operação de negócios #Outro

Choosing an electric dirt bike in Australia has become a smart move for modern riders. Australians now prefer electric options because they are quiet powerful and easy to maintain. From bush trails in New South Wales to open tracks in Western Australia electric dirt bikes are gaining trust. Riders searching for electric dirt bikes Australia want performance reliability and value.

CoolyBikes.com has positioned itself as a reliable source for Australians who want a trusted electric dirt bike. Many buyers compare petrol bikes with electric alternatives and quickly notice the advantages. Electric dirt bikes offer instant torque smooth control and low running costs. This makes them suitable for beginners families and experienced off road riders.

The Surron Light Bee X stands out as one of the most searched models. It delivers strong power balanced handling and impressive battery range. Riders across Sydney Melbourne Brisbane Perth Adelaide Canberra Newcastle Gold Coast Sunshine Coast Hobart and Darwin continue to choose this electric dirt bike for off road use.

 

Why Australians Are Switching to Electric Dirt Bikes

Australian riders are changing preferences due to noise restrictions fuel prices and maintenance costs. An electric dirt bike solves many of these issues. No engine noise allows peaceful riding. No fuel means lower ongoing expenses. Fewer moving parts reduce maintenance stress.

In regions like electric bike Melbourne and electric bike Sydney demand increases because riders want eco friendly solutions. Electric dirt bikes suit private land farms and trail riding. They also allow riders to practice skills without disturbing nearby areas.

Weather conditions in Australia also favor electric bikes. Lithium batteries perform well in moderate temperatures. Riders in Brisbane electric bikes markets enjoy year round riding. Perth e bikes users prefer durability in dry environments. These factors push electric dirt bikes into mainstream use.

Best Electric Dirt Bike Models Available at CoolyBikes

CoolyBikes.com focuses on quality models that meet Australian off road needs. The Surron Light Bee X remains the top choice for riders seeking balanced performance. This electric dirt bike offers strong torque smooth acceleration and excellent trail control.

The Surron Light Bee suits riders who want lighter handling. The Surron Light Bee S is ideal for beginners and younger riders. It offers lower seat height and controlled power delivery. For advanced riders the Surron Ultra Bee provides aggressive performance.

Rerode R1 attracts riders searching for a low cost electric bicycle that still handles dirt paths. Many customers searching cheap electric bikes Australia start here before upgrading. CoolyBikes ensures each model is tested reliable and supported locally.

Electric Dirt Bikes for New Riders and Skilled Riders

Not all riders have the same expectations. Beginners want safety control and comfort. Experienced riders want torque speed and suspension response. Electric dirt bikes satisfy both groups when chosen correctly.

Beginners often choose the Surron Light Bee S. It provides predictable throttle response and easy handling. This helps riders learn balance braking and terrain reading. Riders in electric bikes Adelaide and electric bikes Canberra markets prefer this approach.

Experienced riders choose the Surron Light Bee X for its power and flexibility. Sport mode delivers fast acceleration. Eco mode saves battery. Adjustable suspension supports aggressive trail riding. This versatility makes electric dirt bikes ideal for mixed skill households.

Understanding Performance and Power in Electric Dirt Bikes

Performance matters when choosing an electric dirt bike. Australian riders care about torque hill climbing and top speed. The Surron Light Bee X delivers peak power near eight kilowatts. Torque feels instant which helps on sand mud and steep trails.

Top speed reaches around seventy five kilometers per hour depending on conditions. This is more than enough for off road riding. Riders searching surron light bee x top speed often compare it with petrol bikes.

Electric motors deliver consistent power without gear changes. This improves rider confidence and reduces fatigue. Riders across electric bikes Perth and electric bikes Brisbane markets appreciate this advantage on long rides.

Battery Range Charging and Daily Usability

Battery range defines how long an electric dirt bike can ride. The Surron Light Bee X includes a removable lithium battery. Average range reaches about seventy five kilometers at moderate speed. This suits most Australian trail sessions.

Charging takes around two to three hours. Riders can charge overnight or between rides. Electricity cost remains low compared to fuel. This benefits riders searching affordable electric bicycle solutions.

Battery care is simple. Avoid extreme heat. Do not fully drain often. Store properly. These habits extend battery life for years. CoolyBikes provides guidance to ensure long term performance.

Legal Use and Safety Rules in Australia

Electric dirt bike legality varies across Australian states. Most electric dirt bikes including the Surron Light Bee X are sold for off road use. They are not road legal without modifications and registration.

Riders in NSW Victoria Queensland and Western Australia must follow local transport rules. Private land riding and designated off road areas are permitted. Safety gear remains essential everywhere.

CoolyBikes.com clearly explains intended use. This transparency builds trust and protects buyers. Understanding rules prevents fines and ensures responsible riding.

Buying an Electric Dirt Bike in Major Australian Cities

CoolyBikes serves customers across Australia through online ordering. Riders from electric bike Sydney electric bike Melbourne electric bike Brisbane and electric bike Perth order with confidence. Delivery reaches Adelaide Canberra Newcastle Gold Coast Sunshine Coast Darwin and Hobart.

Search terms like electric bikes near me e bikes near me and e bikes for sale near me often lead to CoolyBikes. City specific interest continues to grow as awareness spreads.

Melbourne riders focus on trail access. Brisbane riders want bush performance. Perth riders value durability. CoolyBikes meets each regional need with consistent support.

Price Planning and Long Term Value

Electric dirt bike pricing depends on power and build quality. Cheap electric cycle options exist but lack durability. A proper electric dirt bike offers better value over time.

Electric bikes cost less to run. No fuel expenses. Fewer service parts. Lower maintenance bills. These savings matter to families and frequent riders.

CoolyBikes helps buyers balance budget and quality. Many customers start with cheap ebikes then upgrade. Choosing wisely at first saves money long term.

Maintenance Needs of an Electric Dirt Bike

Electric dirt bikes require simple maintenance. Brake pads chain lubrication tire checks and battery care form the routine. No engine servicing reduces effort.

The Surron Light Bee X uses quality components that last longer. Replacement parts are available through CoolyBikes. This ensures continued performance.

Australian riders appreciate low downtime. Less maintenance means more riding. This strengthens the appeal of electric dirt bikes.

Rider Community and Lifestyle Benefits

Electric dirt bike ownership connects riders to a growing community. Australian groups share riding tips trail locations and upgrade ideas. Group rides occur across Queensland Victoria and New South Wales.

Electric bikes promote responsible riding due to low noise. Communities accept them more easily. Riders feel confident exploring new areas.

CoolyBikes engages with riders through support and knowledge sharing. This builds loyalty and authority.

Real Australian Customer Reviews

Michael from Newcastle NSW says the Surron Light Bee X offers unmatched control on bush trails. He trusts CoolyBikes support.

Emily from Gold Coast QLD searched electric dirt bikes Australia and found perfect advice at CoolyBikes.

Ryan from Melbourne VIC upgraded from a low cost electric bicycle to the Surron Light Bee X and loves the power.

Khalid from Perth WA praises battery range and torque for desert riding.

Laura from Canberra ACT values honest legal guidance and smooth purchase experience.

Is the Surron Light Bee X street legal in Australia

No it is mainly for off road use unless modified and registered.

How fast is the Surron Light Bee X

It reaches about seventy five kilometers per hour.

Are electric dirt bikes good for beginners

Yes they are easy to control and quiet.

What is the range of the Surron Light Bee X

Around seventy five kilometers depending on riding style.

Can I buy from CoolyBikes anywhere in Australia

Yes delivery is available nationwide.

Are electric dirt bikes expensive to maintain

No maintenance costs are lower than petrol bikes.

Is the battery removable

Yes the battery is removable and easy to charge.

Do electric dirt bikes work on sand

Yes they perform well due to high torque.

What safety gear should I use

Helmet gloves boots and protective clothing.

Are electric dirt bikes quiet

Yes they produce very little noise.

Can kids ride electric dirt bikes

Some models suit younger riders with supervision.

Why choose CoolyBikes

Because of trust clear guidance and Australian focus.

Discussão (0)1
Entre ou crie uma conta para continuar
Artigo
· jan 30 9min de leitura

^SystemPerformance ユーティリティの使用方法

#Administração do Sistema #Desempenho #Dicas e truques #Caché #Ensemble #InterSystems IRIS #InterSystems IRIS for Health

これは InterSystems FAQ サイトの記事です。

^SystemPerformance ユーティリティ (旧：^pButtons)  を使用すると、 InterSystems製品が稼働するプラットフォームに関する詳細なパフォーマンス・データを収集することができます。

収集できるのは以下の情報になります。

・IRIS の設定：構成、ドライブの割り当てなど 
・mgstat：IRISのパフォーマンスメトリック（グローバル参照や物理読み込み、など）
・オペレーティングシステムのリソースとパフォーマンスに関するメトリック
　※Unixの場合は vmstatとiostat、Windowsの場合は パフォーマンスモニター
・その他の有用なメトリック

こちらの記事では、^SystemPerformanceツール（旧：^pButtons）の実行方法と、出力情報の利用方法についてご紹介します。


【実行方法】

※^SystemPerformance の実行にはオペレーティングシステムの管理者権限が必要です。
管理者としてシステムにログインしてから実行してください。特にWindowsで UAC(User Access Control)が有効になっている場合は特別な実行方法が必要になります。詳しくは こちら（IMPORTANT: の箇所）をご確認ください。

★その１：既定のプロファイルを使用する場合

^SystemPerformanceユーティリティにはいくつかの既定のプロファイルが用意されています。プロファイル通りの情報収集を行うのであれば、選択して実行すればすぐに情報収集を行えます。
ターミナルより、以下のように実行します。%SYSネームスペースで実行します。

%SYS>set $namespace= "%SYS"      // または、zn "%SYS"
%SYS>do ^SystemPerformance
Current log directory: c:\intersystems\iris\mgr\
Windows Perfmon data will be left in raw format.
Available profiles:
     1  12hours     - 12 hour run sampling every 10 seconds
     2  24hours     - 24 hour run sampling every 10 seconds
     3  30mins      - 30 minute run sampling every 1 second
     4  4hours      - 4 hour run sampling every 5 seconds
     5  8hours      - 8 hour run sampling every 10 seconds
     6  test        - A 5 minute TEST run sampling every 30 seconds
 
Select profile number to run: 6  // test プロファイルを実行してみます（30秒ごとに5分間情報収集）
Collection of this sample data will be available in 420 seconds.  
    // 420秒後に情報収集が終わります
The runid for this data is 20250819_110952_test.

結果は、mgr フォルダに html 形式で出力されます。　例:ServerName_InstanceName_20250819_110952_test.html
情報収集中複数のファイルが生成されますが、最後に上記htmlにまとめられます

コマンドで実行する場合は、以下のようになります。

// プロファイルの実行（引数にプロファイル名を指定）
set runid=$$run^SystemPerformance("test") 

// もし、html 形式のファイルが生成されていない場合は以下のコマンドで出力します
set sc=$$Collect^SystemPerformance(runid)

// 途中で計測を止めたい場合は以下のコマンドを実行します
// 第1引数：中止するレポートの runid
// 第2引数：1 (default) = ログファイルを削除, 0 = ログファイルを残す
write $$Stop^SystemPerformance(runid,0)

 

タスクマネージャで実行したい場合は、上記コマンド $$run^SystemPerformance を登録してスケジュールを起動します。

管理ポータル： 
[ホーム] > [タスクマネージャ] >[新規タスクスケジュール] より、

１．[タスクスケジューラウィザード] を起動します。
２．[このタスクを実行するネームスペース] ドロップダウン・リストから [%SYS] を選択
３．[タスクタイプ] ドロップダウン・リストから [レガシータスク実行] を選択
４．[実行コード] テキスト・ボックスに以下のコードを入力
５．set ^zmgstat(+$h)=$$run^SystemPerformance("test")
６．[次へ] をクリックし、スケジュールの指定を行います。


★その２：カスタムプロファイルを使用する（例：2秒単位で24時間収集）

// プロファイルの作成(情報取得期間と間隔の定義)
set rc=$$genprofile^SystemPerformance("24:",2)   // 24時間(24:)の間 2秒ごとに収集
                                                 //   第１引数：プロファイルを実行する期間。有効な形式は、"hh:mm", "hh:", "mm"。
                                                 //   第２引数：各サンプルを実行する頻度 (秒単位)
                                                 // このコマンドで24hours_2 というプロファイルが生成されます。
                                                 // 生成されたプロファイルは "do ^SystemPerformance" で確認できます。
// 生成したプロファイルを指定して情報取集の実行
set ^zmgstat(+$h)=$$run^SystemPerformance("24hours_2")
                                                 // ^zmgstat(+$h)に戻り値の runid を記録します。  
                                                 // 結果は、mgr フォルダに html 形式で出力されます。
                                                 // 例:ServerName_IRIS_20230615_132100_24hours_2.html


^SystemPerformance ユーティリティによるデータ収集はシステムのパフォーマンスにほとんど影響を与えません。

ただし、出力ファイルによりディスク容量がいっぱいにならないようにするため、ログディレクトリを本番データとは異なる場所に変更し、蓄積した出力ファイルをそちらに保管するようにしてください。
既定の出力ディレクトリは、<インストールディレクトリ>\mgr ディレクトリですが、以下のコマンドで変更できます。

%SYS>do setlogdir^SystemPerformance("directory")



【結果を参照できる便利なツール】

^SystemPerformance ユーティリティで収集した情報は、 InterSystems 独自のパフォーマンスログ mgstat と、オペレーティングシステムのリソースとパフォーマンスに関するメトリック、の両方を含んだ HTML として生成 されます。
以下で紹介しているツールを使用すると、結果を CSVにエクスポートできるので、Excelで簡単にパフォーマンスグラフを作成することができるようになります。
是非ご利用ください。

・^mypButtons を利用して InterSystems IRIS パフォーマンスをチェックしてみましょう

・YASPE（グラフ表示）
　※Docker Container使わないで使用する方法は以下（Pythonインストールの必要あり）
　https://github.com/murrayo/yaspe/blob/main/README.md#running-without-a-container

 

【参照可能な情報例】

^SystemPerformance ユーティリティは、プラットフォーム固有のレポートを生成します。
以下のドキュメントで、プラットフォーム固有の各レポートのセクションについて説明しています。
パフォーマンス・レポートの詳細

参照可能な情報について、いくつかのセクションで具体的にどのような情報が収集できるのか説明します。
まず、すべてのプラットフォームで生成されるmgstatについてご紹介します。

mgstatの場合、

Glorefs グローバル変数に対する全アクセス回数/秒
RemGrefs リモートデータベースのグローバル変数に対する全アクセス回数/秒
Gloupds グローバル変数に対する変更アクセス(Set,Kill)回数
RemGupds リモートのグローバル変数に対する変更アクセス(Set,Kill)回数
PhyRds データベースファイルに対するブロック読込みI/O回数/秒
PhyWrs ライトデーモンによるデータベースファイルに対するブロック書き込みI/O回数/秒
AddBlk ECPサーバからのリモートグローバル変数のブロック転送回数/秒
Rdratio 1秒当たりの論理ブロック読み取り回数　/ 1秒当たりのデータベースファイルに対するブロック読込みI/O回数
WDTime ライトデーモン書き込み処理時間
Jrnwrts ジャーナルファイルへの書き込みI/O数/秒

※補足
PhyRdsとRdratio：mgstatのデータをグラフ化したPhyRds（物理的読み込み）とRdratio（読み込み比率）
システムパフォーマンスから予想される詳細な情報を把握し、キャパシティプランニングを立てるのに役立ちます。

詳細は以下のドキュメントをご覧ください。
^mgstat を使用したパフォーマンスの監視


次に、Microsoft Windows perfmon ユーティリティ（Windowsパフォーマンスモニタ）で取得できる情報についての紹介です。
perfmonの場合、

Processor(_Total)\% Processor Time 全プロセッサの使用率
Current Disk Queue Length ディスクへのI/O待ち数
Disk Writes/sec ディスクへの1 秒あたりの書き込み回数
Avg. Disk sec/Read 読み込みリクエストを出してから返ってくるまでの時間(1読み込みでかかる時間)
Avg. Disk Read Queue Length Disk Read待ちのキュー
Disk Transfers/sec 秒あたりのRead/Writeの合計
Avg. Disk sec/Write 書き込みリクエストを出してから返ってくるまでの時間(1書き込みでかかる時間)
Avg. Disk Write Queue Length Disk Write待ちのキュー

 

Linuxの場合は、vmstatコマンドでメモリやCPU使用率などの情報を取得します。
vmstat の場合、

procs r 実行可能状態のプロセス数（ランキュー）
b 割り込み不可能なスリープ状態にあるプロセス数
memory swpd 使用中の仮想メモリサイズ、スワップサイズ（KB）
free 空きメモリサイズ（KB）
buff バッファとして使用しているメモリサイズ（KB）
cache キャッシュに使用しているメモリサイズ（KB）
swap si ディスクからスワップインしているメモリサイズ（KB/s）
so ディスクにスワップアウトしているメモリサイズ（KB/s）
io bi ブロックデバイスから受け取ったブロック数（blocks/s）
bo ブロックデバイスに送られたブロック数（blocks/s）
system in クロック割り込みも含む、１秒あたりの割り込み回数
cs １秒あたりのコンテキストスイッチの回数
cpu us カーネルコード以外の実行に使用した時間割合（ユーザー時間、nice 時間を含む）（%）
sy カーネルコードの実行に使用した時間割合（システム時間）（%）
id CPUがアイドル状態の時間割合（%）
wa CPUがI/O待ちの時間割合（%）
st ゲストOSがCPUを割り当てられなかった時間の割合（%）


その他、様々な情報を収集しますので、詳細はドキュメントをご覧ください。
InterSystems IRIS パフォーマンス・データ・レポート (Microsoft Windows プラットフォーム)
InterSystems IRIS パフォーマンス・データ・レポート (Apple macOS プラットフォーム)
InterSystems IRIS パフォーマンス・データ・レポート (IBM AIX® プラットフォーム)
InterSystems IRIS パフォーマンス・データ・レポート (Linux プラットフォーム)


enlightened【ご参考】

パフォーマンス低下時の情報収集ツールについて
^SystemPerformance を使用したパフォーマンスの監視

Discussão (0)0
Entre ou crie uma conta para continuar
Artigo
· jan 29 6min de leitura

使用 IAM 通过 OAuth 2.0 确保 FHIR 服务器的安全

#FHIR #InterSystems API Manager (IAM) #OAuth2 #InterSystems IRIS for Health

InterSystems API 管理器（IAM）是 InterSystems IRIS 数据平台的核心组件，提供集中式 API 管理，重点强调安全性。IAM 简化了从创建到退出的整个 API 生命周期，并提供了一个开发人员门户，便于发现和集成 API。访问控制功能允许管理员定义精确的权限，IAM 与 IRIS 数据平台无缝集成，增强了数据管理和集成能力。

IAM 的功能包括

  • API 网关：集中式 API 管理和安全中心。
  • API 生命周期管理：从创建到退出的完整生命周期控制。
  • 安全性：身份验证、授权和数据加密。
  • 监控和分析：使用监控和模式分析工具。
  • 开发人员门户网站：具有文档和测试功能的 API 发现门户。
  • 访问控制：对 API 访问和操作进行细粒度控制。
  • 与 InterSystems IRIS 集成：与 IRIS 数据平台无缝集成。

使用案例： 本报告中的用例是身份和访问管理。

符合 OAuth 2.0 标准的身份验证和授权，使用 IAM 确保 FHIR 服务器的安全。

在本文档中，您将了解如何使用 InterSystems API Manager 通过 OAuth 2.0 确保 FHIR 服务器的安全。OAuth 2.0 是一种广泛使用的授权标准，可使应用程序访问 FHIR 服务器上受保护的资源。InterSystems API 管理器是一种可简化 FHIR API 的创建、管理和监控的工具。按照本文档中的步骤，您将能够配置 InterSystems API Manager 作为 OAuth 2.0 授权服务器，并向授权客户端授予访问令牌。您还将了解如何使用客户端库，使用 OAuth 2.0 将应用程序连接到 FHIR 服务器。

注意：FHIR 服务器仅支持用于 OAuth 2.0 身份验证的 JWT 标记，不支持不透明标记。

本地运行演示的说明：

  1. 在 "命令提示符 "中运行以下命令克隆相关版本库： 
    git clone https://github.com/isc-padhikar/IAM_FHIRServer
  2. 进入新克隆的版本库目录，创建一个新目录并命名为 "key"。然后复制一个 iris.key 文件，这是支持 API 管理的 InterSystems IRIS for Health 的许可证。
  3. 然后返回命令提示符，逐个运行以下命令： 
    docker-compose build
docker-compose up
  4. 转到运行 IAM 的 localhost:8002。
  5. 使用 IAM，我可以将 FHIR 服务器作为服务提供，如下图所示：
  6. 定义一个路由，作为 FHIR 服务器的代理（我已将 /fhir 定义为代理），如下图所示：
  7. 然后，定义插件，用于处理向 FHIR 服务器发出的请求、验证和授权对 FHIR 服务器的访问。我们应在 JWT 插件的 "凭据 "部分定义 JWT 令牌的发行方（授权服务器）和通过解码私钥获得的公钥（请参阅即将介绍的 "授权服务器 "部分），如下图所示： 下图显示了使用 Auth0 服务器进行的身份验证和通过 IAM 进行的基于 JWT 令牌的授权。从授权服务器获取 JWT 令牌：使用 JWT 令牌通过 IAM 中定义的代理路由访问 FHIR 服务器：

授权服务器：

使用外部授权服务器及其 Auth0。在接下来的 "用作参考的演示 "部分提到的演示 #1 (FHIROktaIntegration) 的 README 中给出了设置授权服务器的说明。

获取 JSON 网络密钥集 (JWKS) 的端点：https://dev-bi2i05hvuzmk52dm.au.auth0.com/.well-known/jwks.json

它为我们设置的授权服务器提供了一对密钥，可用于使用解码算法检索私钥。

我们将在 IAM 中使用私钥验证 JWT 令牌签名。

从 JWKS 获取公钥的最佳做法是使用编程语言。我在 Python 中使用了以下代码：

import base64
from cryptography.hazmat.backends import default_backend
from cryptography.hazmat.primitives import serialization
from cryptography.hazmat.primitives.asymmetric import rsa
import requests
# Replace 'YOUR_DOMAIN' with your actual Auth0 domain
jwks_url = 'https://dev-bi2i05hvuzmk52dm.au.auth0.com/.well-known/jwks.json'
response = requests.get(jwks_url)
jwks = response.json()
# Choose a specific key from the JWKS (e.g., the first key)
selected_key = jwks['keys'][0]
# Decode 'AQAB' (exponent 'e') from Base64 URL-safe to integer
decoded_exponent = int.from_bytes(base64.urlsafe_b64decode(selected_key['e'] + '==='), byteorder='big')
decoded_modulus = int.from_bytes(base64.urlsafe_b64decode(selected_key['n'] + '==='), byteorder='big')
# Construct the RSA public key
public_key = rsa.RSAPublicNumbers(
    decoded_exponent,
    decoded_modulus
).public_key(default_backend())
# Convert the public key to PEM format
public_key_pem = public_key.public_bytes(
    encoding=serialization.Encoding.PEM,
    format=serialization.PublicFormat.SubjectPublicKeyInfo
)
print(public_key_pem.decode('utf-8'))

用作参考的演示：

  1. FHIROktaIntegration:https://openexchange.intersystems.com/package/FHIROktaIntegration该演示展示了如何直接在 InterSystems IRIS for Health 上配置 OAuth 2.0，并将该配置用于 FHIR 服务器。请按照说明配置授权服务器的详细信息。不过，配置完成后在管理门户中是这样的： 这展示了如何在 InterSystems IRIS for Health 中配置 OAuth2.0 以确保 FHIR 服务器的安全。
  2. IAM 从零到英雄：https://openexchange.intersystems.com/package/iam-zero-to-hero

该演示包括 IAM 和 IAM 相关培训。我将对其进行修改，使其具有 FHIR 服务器，并在此演示中使用 IAM 实例与 Auth0 授权服务器进行身份验证，并使用 JWT 插件授权访问。
与之前的演示不同，这次演示使用 IAM 公开 FHIR 服务器端点，并使用 IAM 提供的插件库通过 OAuth 2.0 标准确保其安全。

本演示中的更改：

在本演示中，我在 IRIS for Health 实例中添加了 FHIR 服务器。请用以下代码替换 iris.script 文件中的代码：

;do $System.OBJ.LoadDir("/opt/irisapp/src","ck",,1)
zn "%SYS"
Do ##class(Security.Users).UnExpireUserPasswords("*")
set $namespace="%SYS", name="DefaultSSL" do:'##class(Security.SSLConfigs).Exists(name) ##class(Security.SSLConfigs).Create(name) set url="https://pm.community.intersystems.com/packages/zpm/latest/installer" Do ##class(%Net.URLParser).Parse(url,.comp) set ht = ##class(%Net.HttpRequest).%New(), ht.Server = comp("host"), ht.Port = 443, ht.Https=1, ht.SSLConfiguration=name, st=ht.Get(comp("path")) quit:'st $System.Status.GetErrorText(st) set xml=##class(%File).TempFilename("xml"), tFile = ##class(%Stream.FileBinary).%New(), tFile.Filename = xml do tFile.CopyFromAndSave(ht.HttpResponse.Data) do ht.%Close(), $system.OBJ.Load(xml,"ck") do ##class(%File).Delete(xml)

//init FHIR Server
zn "HSLIB"
set namespace="FHIRSERVER"
Set appKey = "/csp/healthshare/fhirserver/fhir/r4"
Set strategyClass = "HS.FHIRServer.Storage.Json.InteractionsStrategy"
set metadataPackages = $lb("hl7.fhir.r4.core@4.0.1")
set importdir="/opt/irisapp/src"
//Install a Foundation namespace and change to it
Do ##class(HS.Util.Installer.Foundation).Install(namespace)
zn namespace

// Install elements that are required for a FHIR-enabled namespace
Do ##class(HS.FHIRServer.Installer).InstallNamespace()

// Install an instance of a FHIR Service into the current namespace
Do ##class(HS.FHIRServer.Installer).InstallInstance(appKey, strategyClass, metadataPackages)

// Configure FHIR Service instance to accept unauthenticated requests
set strategy = ##class(HS.FHIRServer.API.InteractionsStrategy).GetStrategyForEndpoint(appKey)
set config = strategy.GetServiceConfigData()
set config.DebugMode = 4
do strategy.SaveServiceConfigData(config)

zw ##class(HS.FHIRServer.Tools.DataLoader).SubmitResourceFiles("/opt/irisapp/fhirdata/", "FHIRSERVER", appKey)

zn "USER"
zpm "load /opt/irisbuild/ -v":1:1
zpm 
load /opt/irisapp/ -v
q
do ##class(Sample.Person).AddTestData()
halt

2. 在 docker-compose.yml 文件中，将 IAM 的镜像更新为最新版本（containers.intersystems.com/intersystems/iam:3.2.1.0-4），因为只有 3.1 以来的 IAM (Kong) 版本才支持 JSON draft-6，而这正是 FHIR 规范所提供的。

Discussão (0)1
Entre ou crie uma conta para continuar
Anúncio
· jan 29

Beta testers needed for our upcoming InterSystems CCR EHR Application Specialist certification exam

#CCR #TrakCare

Hello InterSystems EHR community, 

InterSystems Certification is currently developing a certification exam for CCR Tier 2 users, and if you match the exam candidate description below, we would like you to beta test the exam! The exam will be available for beta testing starting January 27, 2026. 

Beta testing will be completed March 28, 2026.

What are my responsibilities as a beta tester?

As a beta tester, we ask that you schedule and take the exam by March 28, 2026. The exam will be administered in an online proctored environment free of charge (the standard fee of $150 per exam is waived for all beta testers). The InterSystems Certification team will then perform a careful statistical analysis of all beta test data to set a passing score for the exam. The analysis of the beta test results typically takes 6-8 weeks, and once the passing score is established, you will receive an email notification from InterSystems Certification informing you of the results. If your score on the exam is at or above the passing score, you will have earned the certification!

Note: Beta test scores are completely confidential. 

Interested in participating? Read the Exam Details below. 

Exam Details

Exam title: InterSystems CCR EHR Application Specialist

Note: InterSystems now offers two EHR products built by the same team and based on the same systems and processes. TrakCare serves as the foundational platform, while IntelliCare extends this foundation with additional features and capabilities. Both products share the same core infrastructure. Therefore, when referring to features common to both products - such as those covered in exam topic list - the term InterSystems EHR is used.  

Candidate description: An EHR application specialist who:: 

  • Uses Tier 2 CCRs to document and process change workflows,
  • Makes configuration changes in InterSystems EHR, and
  • Transports and deploys configuration changes across environments.

Recommended practical experience: Independently progress at least 50 Tier 2 CCRs and/or approximately 6 months full-time usage.

Recommended Preparation: Review the following:

Exam practice questions: A set of practice questions is provided here to familiarize candidates with question formats and approaches.

Number of questions: 81

Time allotted to take the exam: 2 hours

Exam format: Questions are presented in two formats: multiple choice and multiple response.

System requirements for beta testing

  • Working camera & microphone
  • Dual-core CPU
  • At least 2 GB available of RAM memory
  • At least 500 MB of available disk space
  • Minimum internet speed:
    • Download - 500kb/s
    • Upload - 500kb/s

Exam topics and content

The exam contains questions that cover the areas for the stated role as shown in the exam topics chart immediately below:

 

General Concepts (14) CCR Tier 0 (21) CCR Transport (19) CCR Tier 2 (27)

1. Describes basic change control concepts

  1. Defines change control as a concept
  2. Discusses the benefits of change control and the risks of not having it
  3. Defines source control alone and in the context of change control
  4. Names tips for successful use of change control

2. Describes change control with InterSystems

  1. Describes change control tools used within InterSystems including CCR and Perforce

3. Describes CCR and its main concepts

  1. Defines CCR First Principles
  2. Identifies the workflow order between the 4 possible CCR Primary environments
  3. Defines the term CCR system
  4. Defines the term CCR Transport and describes the movement of changes between environments, CCR, and Perforce
  5. Defines the terms Perforce branch, Item, and ItemSet
  6. Describes CCR Usage Tiers and gives examples

4. Performs basic tasks in CCR

  1. Navigates the CCR homepage, main menu, and main pages
  2. Accesses documentation and FAQs
  3. Defines the terms State, Phase, and Transition

1. Progresses a Tier 0 CCR

  1. Defines the terms Organization, Responsible Organization, Site Code, System, and System Code
  2. Creates a Tier 0 CCR Record
  3. Describes use of fields available when creating a CCR
  4. Recalls who can pass peer reviews in the CCR workflow from IN_PREP to CLOSED
  5. Documents every state from In_PREP to Closed in a BASE-TEST-LIVE workflow including peer reviews
  6. Selects the correct transition for deferred deployments.
  7. Transitions CCRs to the next state
  8. Performs the markPREPComplete transition
  9. Identifies the workflow for failPeerReview
  10. Performs the markAcceptanceFailed
  11. Describes markValidationFailed transition, including best practices
  12. Describes the importance of Peer Reviews
  13. Describes the importance of closing CCRs
  14. Recalls in which state an authorization is needed to progress a CCR
  15. Implements and tests changes in correct states of the workflow
  16. Locates and uses CCR Transition History
  17. Identifies and uses the env token

2. Uses Auxiliary Tools and Transitions

  1. Reassigns CCRs
  2. Describes the effect of Peer Review routing configuration options including System Architects and Default Peer Reviewers
  3. Recalls when a CCR can and cannot be merged
  4. Performs merge transitions and interprets results

1. Describes CCR Transport Basics

  1. Describes CCR Client Tools
  2. Describes CCR Transport workflows for disconnected environments, including uploading ItemSets from BASE to CCR and deploying ItemSets from CCR to TEST/LIVE
  3. Deploys ItemSets using best practices
  4. Describes the automatic preview integration on passPeerReview transition
  5. Identifies states and transitions with possible Perforce and/or ItemSet activity
  6. Uses CCR Transport best practices including the importance of cancelling CCRs properly

2. Describes CCR Transport Tools and terminology in the CCR Record

  1. Defines the term changelist
  2. Locates and identifies available meta data for submitted changes
  3. Logs into Perforce in CCR
  4. Describes diff chunks and merge conflicts
  5. Finds and interprets list of ItemSets associated with a CCR
  6. Defines and identifies the importance of baselining

3. Describes CCR best practices and debugging techniques

  1. Uses Catch-up CCRs
  2. Uses the revision history
  3. Locates and interprets error messages
  4. Uses transport log to retrieve additional error details
  5. Identifies cause and solution for merge conflicts
  6. Identifies and describes how to resolve errors in bundle and upload validation
  7. Describes options if uploaded to wrong CCR

1. Uses Tier 2 CCRs to safely progress changes made in InterSystems EHR applications

  1. Identifies when it is appropriate to create a change session in BASE
  2. Recalls what is required in order to create a change session
  3. Uses Change Control Menu within the InterSystems EHR side menu (bundle list)
  4. Uses the Find GUID tool
  5. Uses the Change Control menu to undo changes in the correct order
  6. Uses the Change Control screen to bundle and upload changes
  7. Identifies how security groups impact the visibility of Change Control menus
  8. Recalls the importance of the exclusion list
  9. Recalls how Code Table Overrides impact configuration changes
  10. Identifies how and when to deploy ItemSets in workflow

2. Recalls features of the CCR Tier 2 User Interface

  1. Identifies whether a source control issue is related to TCC
  2. Identifies whether a source control issue is related to CCR
  3. Recalls the function of the GUID Prediction in the CCR UI
  4. Recalls the importance of the "Create ItemSet" button in the Perforce Details section
  5. Recalls when to use the "Perforce Integration" feature in the Perforce Details section

3. Debugs CCR errors

  1. Distinguishes between primary key and GUID
  2. Recalls what ElementXML is and how to view it
  3. Identifies scenarios where support needs to be contacted
  4. Recalls why an ItemSet does not show up in an ItemSet list
  5. Recalls what an Advanced reassign is
  6. Recalls what to do when an itemset becomes stale
  7. Recalls what to do when a token becomes invalid
  8. Cancels and backs out of CCRs
  9. Uses the Restore To Base flag
  10. Resolves circular dependencies between CCRs
  11. Resolves missing GUID errors
  12. Identifies cause and solution for misaligned GUIDs

 

Instructions: 

Please review the following instructions for scheduling and buying an exam:

  1. From our exam store, log in with your InterSystems Single Sign-On (SSO) account.
    1. If necessary, please register for an account.
  2. Select InterSystems CCR EHR Application Specialist - Beta (CCE-Beta) and click Get Started.
  3. Verify system compatibility as instructed. The Safe Exam Browser download requires administrative privileges on your device.
  4. Run the setup test to ensure the device satisfies the exam requirements.
  5. Schedule your exam – this must be done before checking out. The exam must be taken at least 24 hours after, but within 30 days, of scheduling the exam.
  6. Review the InterSystems Certification Program Agreement.
  7. Confirm your appointment. You will receive an email from Certiverse with your exam appointment details.
  8. You can access your reservations and history through the Exam Dashboard available through the MY EXAMS menu.

Below are important considerations that we recommend to optimize your testing experience:

  • Read the Taking InterSystems Exams and Exam FAQs pages to learn about the test-taking experience.
  • Read the InterSystems Certification Exam Policies.
  • On the day of your exam, log in to Certiverse at least 10 minutes before your scheduled time, launch the exam under MY EXAMS, and wait for the proctor to connect.
  • Please have your valid government ID ready for identification. The proctor will walk you through the process of securing your room and releasing the exam to you. 

You may cancel or reschedule your appointment without penalty as long as the action is taken at least 24 hours in advance of your appointment. The voucher code will reactivate and you can use it to reschedule the exam.

Please contact certification@intersystems.com if you have any questions or need assistance, and we encourage you to share any feedback about the exam, whether positive or negative.

Discussão (0)1
Entre ou crie uma conta para continuar