Nova postagem

Pesquisar

Artigo
· Mar. 6 1min de leitura

Evitad usar el paquete llamado «code» con métodos python incrustados usando [Language = python].

Hola,

como me tomó algún tiempo para averiguar lo que está mal, me gustaría compartir esta experiencia, para que no caigáis en la misma trampa.

Acabo de darme cuenta de que si nombráis a vuestro paquete «code» (todo en minúsculas), en una clase que usa algo de python embebido usando [Language = python], os encontraréis con la <THROW> *%Exception.PythonException <PYTHON EXCEPTION> 246 <class 'ModuleNotFoundError'>: No module named 'code.basics'; 'code' is not a package

Class code.basics Extends %RegisteredObject
{

ClassMethod Welcome() As %Status [ Language = python ]
{
print('Welcome!')
return True
}
}
IRISAPP>w ##class(code.basics).Welcome()

W ##CLASS(code.basics).Welcome()
^
<THROW> *%Exception.PythonException <PYTHON EXCEPTION> 246 <class 'ModuleNotFoundError'>: No module named 'code.basics'; 'code' is not a package

Funciona bien con "Code" :

Class Code.basics Extends %RegisteredObject
{

ClassMethod Welcome() As %Status [ Language = python ]
{
print('Welcome!')
return True
}
}
IRISAPP>w ##class(Code.basics).Welcome()
Welcome!
1
Discussão (0)1
Entre ou crie uma conta para continuar
Job
· Mar. 6

Principal Architect and Integration Engineer

Role: Principal Architect and Integration Engineer

Employment Type: Full Time 

Note: Expertise in Rhapsody/Intersystems is Mandatory.

 

Main Responsibilities  

  1. Technology Strategy Key contributor to the technology strategy for the business, setting a north star, and driving excellence for our adoption and implementation of technologies to deliver Data Sharing/Integration, API Enablement, and Data Migration Services now and into the future. 
  1. Customer Facing This technical leader will represent technology in the public eye, can think quick on their feet and are a confidence building communicator in client meetings and events. They will be active in supporting account meetings, project status reviews, presales, and marketing. 
  1. Delivery Best Practices They will ensure a high bar is set for best practices, where good enough is not good enough, teams challenge themselves to keep improving and a comprehensive set of methodologies and standards is used across all client engagements.  
  1. Engineering & Delivery Personnel Working with our global Development Centres they will ensure that in recruitment we attract and bring in the best talent, including getting hands-on with recruitment activities. Setting objective parameters for staff development and grading, ensuring that staff are developed to their potential and prepared for new grades or promotions.  
  1. Measurable Outcomes Establish and maintain key performance metrics that measure effectiveness of technology, people development and best practices. 
  1. Architecture, Planning & Delivery They will oversee the architecting of client solutions, planning and contribute to client engagements with our development centres and manage the efficacy of any third-party vendor relations. When required they will leverage their technical expertise to design and build solutions in appropriate technologies, taking the role of a senior developer/architect. 
  1. Innovation Stays abreast of contemporary trends in technology. They will need to keep up with market trends and identify new opportunities for the company, ensuring these align with business goals and the needs of our client base.  
  1. Compliance, Regulation & Cyber Security Creating, improving, and reinforcing both VLSI only and company-wide policies, procedures, and best practices to ensure compliance with industry regulation and Cyber Security. 
1 Comment
Discussão (1)2
Entre ou crie uma conta para continuar
Pergunta
· Mar. 5

如何下载5.2.4版本cache

如何下载5.2.4版本cache

1 Comment
Discussão (1)2
Entre ou crie uma conta para continuar
Pergunta
· Mar. 5

HL7 search and replace and adding extra carriage return/line feed after a segment - resolved

Sample with multiple Items;

 

MSH|^~\&|GMRC IF CONSULT|XXX^XXXXX^DNS|GMRC IF CONSULT|YYY^^DNS|20250123175341+0000|CRNR|ORM^O01^ORM_O01|Q5808332894T6790522104|T|2.3|||State|State|USA

PID|1||1013570973V041977^^^ICN^ID~1110106796^^^EDIPI^EDIPI||PROSTEST^EHR||19760902|M||||||||||129256619|678235672

ORC|NW|15207778763^XXX^GMRCIFR|||||^^^20250123175300+0000^^R||20250123175331+0000|XXX8051652^PCP1^Physician||XXX8051652^PCP1^Physician|||20250123175341+0000||YYY

OBR|1|15207778763^XXX^GMRCIFR||YYY^PROSTHETICS IFC^757Office1235||20250123175300+0000||||||||||XXX8051652^PCP1^Physician|||Implant Usage (PSAS)||||||||^^^20250123175300+0000

OBX|1|TX|2000.02^REASON FOR REQUEST^AS4|1|Implant Usage (PSAS)||||||O

OBX|1|TX|2000.02^REASON FOR REQUEST^AS4|2|REASON FOR REQUEST: Item Number: 00801741016608||||||O   <<<< Remove ALL instances of “REASON FOR REQUEST:”

OBX|1|TX|2000.02^REASON FOR REQUEST^AS4|3|REASON FOR REQUEST:      Transaction Date/Time: 01/22/2025 17:45||||||O

OBX|1|TX|2000.02^REASON FOR REQUEST^AS4|4|REASON FOR REQUEST:      Station Number: 757||||||O

OBX|1|TX|2000.02^REASON FOR REQUEST^AS4|5|REASON FOR REQUEST:      Item Description: Plug Surgical 1.3in Groin Monofilament ||||||O

OBX|1|TX|2000.02^REASON FOR REQUEST^AS4|6|REASON FOR REQUEST: Nonabsorbable Perfix Polypropylene Medium Taper 1.55in Sterile Hernia ||||||O

OBX|1|TX|2000.02^REASON FOR REQUEST^AS4|7|REASON FOR REQUEST: Repair 0112760||||||O

………… continued

OBX|1|TX|2000.02^REASON FOR REQUEST^AS4|128|REASON FOR REQUEST: Item Number: 00380650697127||||||O

OBX|1|TX|2000.02^REASON FOR REQUEST^AS4|129|REASON FOR REQUEST:      Transaction Date/Time: 01/23/2025 16:10||||||O

OBX|1|TX|2000.02^REASON FOR REQUEST^AS4|130|REASON FOR REQUEST:      Station Number: 757||||||O

OBX|1|TX|2000.02^REASON FOR REQUEST^AS4|131|REASON FOR REQUEST:      Item Description: Lens SP PmmA 5.25x12.0mm (5) +13.0D||||||O

OBX|1|TX|2000.02^REASON FOR REQUEST^AS4|132|REASON FOR REQUEST:      Manufact urer: ALCON||||||O

OBX|1|TX|2000.02^REASON FOR REQUEST^AS4|133|REASON FOR REQUEST:      Manufacturer Model Number: LX10BD 13.0||||||O

OBX|1|TX|2000.02^REASON FOR REQUEST^AS4|134|REASON FOR REQUEST:      HCPCS:||||||O

OBX|1|TX|2000.02^REASON FOR REQUEST^AS4|135|REASON FOR REQUEST:      Lot Number: 01232025||||||O

OBX|1|TX|2000.02^REASON FOR REQUEST^AS4|136|REASON FOR REQUEST:      Expiration Date/Time: 02/28/2025 05:00||||||O

OBX|1|TX|2000.02^REASON FOR REQUEST^AS4|137|REASON FOR REQUEST:      Serial Number: 01232025||||||O

OBX|1|TX|2000.02^REASON FOR REQUEST^AS4|138|REASON FOR REQUEST:      Source: 757-TrackCore Inv||||||O

OBX|1|TX|2000.02^REASON FOR REQUEST^AS4|139|REASON FOR REQUEST:      Used Quantity:           0||||||O

OBX|1|TX|2000.02^REASON FOR REQUEST^AS4|140|REASON FOR REQUEST:      Waste Quantity:           0||||||O

OBX|1|TX|2000.02^REASON FOR REQUEST^AS4|141|REASON FOR REQUEST:      Unit Cost:           0.00||||||O

OBX|1|TX|2000.02^REASON FOR REQUEST^AS4|142|REASON FOR REQUEST:      Total Cost:           0.00      <<<<<<||||||O     Add a line break but only on messages with multiple “Item Number:”.

OBX|1|TX|2000.02^REASON FOR REQUEST^AS4|143|Special Instructions: ||||||O

OBX|2|CE|^PROVISIONAL DIAGNOSIS|1|R52^Pain, unspecified^I10||||||O

NTE|P|UCID:757_15207778763

 

Req 1

Add line breaks to OBX 5 segment with  Prosthetics orders contains "Issued in Clinic (PSAS)" OR "Implant Usage (PSAS)" with multiple items but Not messages with only one Item

Example

 

 

Req 2

Remove repeating text "REASON FOR REQUEST:" in OBX 5, with Prosthetics orders contains "Issued in Clinic (PSAS)" OR "Implant Usage (PSAS)".

Description: If PSAS order type is "Implant Usage (PSAS)" OR PSAS Order type is "Issued in Clinic (PSAS)" then remove string "REASON FOR REQUEST:" from OBX-5 fields where string "REASON FOR REQUEST:" is found.

15 Comments
Discussão (15)3
Entre ou crie uma conta para continuar
Anúncio
· Mar. 5

[Video] Energy Consumption for AI

Hey Community!

We're happy to share the next video in the series dedicated to Gen AI on our InterSystems Developers YouTube:

⏯ Energy Consumption for AI

Explore the energy demands of AI technologies and major tech companies' growing investments in nuclear power to sustain AI advancements. Learn how to optimize AI energy usage:

  • Use only what you need – limit energy consumption where possible.
  • Use the right tool for the job – avoid unnecessary AI use when simpler solutions suffice.
  • Consider scale – design AI technologies with global adoption and efficiency in mind.

🗣  Presenter: @Jess Jowdy, Manager of Healthcare Sales Engineering, InterSystems

Enjoy watching, and look forward to more videos! 👍

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