Nova postagem

Pesquisar

Anúncio
· 5 hr atrás

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

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
Artigo
· 7 hr atrás 3min de leitura

importação direta arquivo excel para global

Pessoal, a quem interessar possa.....

Desenvolvi uma Classe utilizando o python para ler um arquivo excel e gravar o conteúdo em global. Vejam como ficou: (fiquem a vontade para melhorias ou ajustes)

Class Utils.Importador Extends %RegisteredObject
{ /// Importa uma planilha Excel para a global ^ExcelData
/// Parâmetro: caminhoArquivo (Ex: "C:\Temp\dados.xlsx")
/// Exemplo de uso: Do ##class(Utils.Importador).LerExcel("C:\Temp\minha_planilha.xlsx",$username)
ClassMethod LerExcel(caminhoArquivo As %String, nomeUsuario As %String) [ Language = python ]
{
    import os
    try:
        from openpyxl import load_workbook
        import iris         if not os.path.exists(caminhoArquivo):
            print(f"ERRO: Arquivo não encontrado: {caminhoArquivo}")
            return         print(f"\n--- Lendo arquivo: {caminhoArquivo} ---")
        
        wb = load_workbook(caminhoArquivo, data_only=True)
        ws = wb.active
         
        
        # Limpa global
        g_ref = iris.gref('^ExcelData')
        del g_ref[nomeUsuario]
        
        count = 0
        for row in ws.iter_rows(min_row=2, values_only=True):
            count += 1
            lista_dados = []
            for celula in row:
                if celula is None:
                    lista_dados.append("")
                else:
                    lista_dados.append(str(celula))
            
            dados_para_gravar = "|".join(lista_dados)             if count == 1:
                print(f"Gravando (formato string IRIS): {dados_para_gravar}")
            g_ref[nomeUsuario,count] = dados_para_gravar
                
        print(f"Sucesso! {count} linhas gravadas em ^ExcelData.")     except Exception as e:
        print(f"ERRO: {e}")
} }
 

Discussão (0)1
Entre ou crie uma conta para continuar
Anúncio
· 8 hr atrás

Videos for InterSystems Developers Annual 2025 Recap

Hello and welcome to the 2025 Developer Community YouTube Recap.
Top 10 videos from InterSystems Ready 2025
InterSystems Different by Design
By Scott Gnau, Peter Lesperance, Tom Woodfin, Gokhan Uluderya, Jeff Fried, Daniel Franco
Analytics and AI with InterSystems IRIS - From Zero to Hero
By Benjamin De Boe, Thomas Dyar, Carmen Logue
The Road to AI in Healthcare
By Don Woodlock, Sean Kennedy, Alex MacLeod, Erica Song, James Derrickson, Julie Smith, Kristen Nemes, Varun Saxena, Dimitri Fane, Jonathan Teich, Judy Charamand
Using SerenityGPT to Build Out an Application GenAI Middleware at InterSystems
By Ben Spead, Hannah Sullivan, Dean Andrews, Victor Naroditskiy
Top 10 videos from InterSystems Contests
Claude IRIS Interoperability
By Dmitry Maslennikov
BG Iris Agent
By Elena Karpova
Quarkus IRIS Monitor
By Davi Massaru Teixeira Muta
IPM Explorer for VSCode
By John McBride
Langchain IRIS Tool
By Yuri Marx
iris_io_utility
By Pietro Di Leo
yaml-adaptor
By Yuri Marx
Global Inspector
By Robert Cemper
 
 
Top 10 "Code to Care" videos by Don Woodlock, President of InterSystems
"Rarified Air" videos by John Paladino, Vice President of Client Services, InterSystems
Securing the Digital Front Door
Top 10 other videos
FHIR as an AI platform: EHRs, Simulations, and Safety
By Elijah Cotterrell, Duc Lanwyn, Lydia Patterson, Michael Curtis
By Evgeny Shvarov
Discussão (0)1
Entre ou crie uma conta para continuar
Artigo
· 10 hr atrás 3min de leitura

Mejoras en la aplicación CCR para buenas prácticas

Durante el último año, el equipo de desarrollo de CCR ha priorizado cambios en la aplicación CCR para mostrar y fomentar mejores prácticas en su uso. Este artículo destaca algunas de las áreas en las que nos hemos centrado:

  • Panel de organización
  • Alertas del sistema
  • Higiene de ramas

En cada una de estas áreas, hemos aumentado la visibilidad de posibles problemas en el uso de CCR y proporcionado herramientas para que los usuarios los aborden de manera proactiva.

Panel de organización

Hemos seguido ampliando la información disponible en la página de detalles de la organización.

La vista general es un excelente lugar para obtener una visión global del uso de CCR en vuestra organización. Ahora incluye más indicadores clave (KPIs) que destacan distintas áreas de atención y enlazan a las páginas de la aplicación CCR donde podéis solucionarlas.

La pestaña Sistemas ofrece información detallada sobre el estado de las Client Tools en todos los entornos, así como información de System Architect. Las alertas aquí señalan información faltante, inactividad y Client Tools desactualizadas, con enlaces a los sistemas correspondientes.

Otras pestañas de la página de detalles de la organización se han mejorado con información adicional para que el uso de CCR en vuestra organización sea claro de un vistazo.

Alertas del sistema

Otra área con mayor visibilidad es la página de detalles del sistema, donde ahora tenemos alertas para muchos problemas de uso de CCR.

Se han añadido alertas de entorno para URLs no configuradas, URLs inseguras y problemas detectados en Client Tools. Los detalles se muestran al pasar el cursor por encima.

Cuando CCR detecta que las Client Tools del sistema están desactualizadas, aparecerá una alerta para incentivar el uso del botón de actualización.

Los sistemas que no hayan tenido actividad durante 6 meses ahora mostrarán una alerta. Dicho sistema puede ser dado de baja si ya no se utiliza, o se puede hacer clic en el botón de posponer para contar como un sistema activo durante el próximo año. Esto es adecuado para algunos tipos de sistemas que rara vez necesitan recibir actualizaciones.

Higiene de ramas del sistema

La higiene de ramas del sistema es una herramienta potente para identificar problemas existentes en las ramas de Perforce de un sistema. Está disponible en la página de detalles del sistema para cada sistema de nivel 1 o 2.

La funcionalidad principal de la herramienta ha estado disponible durante algún tiempo, pero las mejoras recientes han perfeccionado la detección de algunos casos límite.

Ejecutar esta comprobación en un sistema maduro es una excelente manera de identificar posibles problemas que podrían surgir en el futuro.

Conclusión

En estas áreas y en toda la aplicación CCR, se han realizado muchos cambios este año con el objetivo de promover el mejor uso de CCR. Las mejoras futuras se centrarán en mostrar más información y desarrollar herramientas que ayuden a los usuarios de CCR a comprender mejor sus sistemas y resolver problemas de manera proactiva.

Si tenéis preguntas o sugerencias sobre cómo la aplicación CCR puede fomentar las buenas prácticas, por favor, dejad un comentario abajo.

Discussão (0)1
Entre ou crie uma conta para continuar
Pergunta
· 12 hr atrás

How to Write Cold Email Templates That Actually Get Replies

Introduction: Why Most Cold Emails End Up Ignored

I still remember the first cold email I ever sent.

I spent nearly an hour perfecting it polishing the wording, adding buzzwords, and convincing myself it sounded “professional.” I hit send, waited… and heard nothing. No reply. No rejection. Just silence.

That’s when it hit me: cold email isn’t about sounding impressive it’s about sounding human.

If you’re exploring IT, sales, or client-facing roles, learning how to write cold email templates that actually get replies is a skill worth mastering. Whether you’re reaching out for prospecting, building business connections, or client acquisition, the difference between ignored emails and real conversations comes down to how you approach the message.

Let’s break it down in a way that feels real not robotic.

 

First, Understand the Real Goal of a Cold Email

Here’s a mistake beginners make (I did too):
They think the goal of a cold email is to sell.

It’s not.

The real goal of a cold email is to start a conversation.

You’re not closing deals in one email. You’re opening a door. When you shift your mindset from “sales emails” to human outreach, response rates naturally improve.

Think of it like introducing yourself at a tech meetup. You wouldn’t launch into a pitch you’d start with something relatable.

 

Why Most Cold Email Templates Fail

Before we talk about what works, let’s be honest about what doesn’t.

Most cold email templates fail because they:

  • Sound copy-pasted or overly scripted
  • Focus too much on the sender, not the reader
  • Try to do too much in one message
  • Feel like mass outreach instead of a personal note

People can spot generic cold emails instantly especially potential clients who receive dozens of them daily.

Your job is to feel different without trying too hard.

 

Start With a Subject Line That Feels Natural

Your subject line doesn’t need to be clever. It needs to be believable.

Some examples that work better than flashy headlines:

  • “Quick question about your team”
  • “Thought this might be relevant”
  • “Intro   no pitch”

In IT and business environments, simple and respectful subject lines often outperform aggressive ones. You’re signaling, “I’m a real person, not automation.”

That alone boosts open and response rates.

 

Write Like You Talk (Yes, Really)

This is where many cold email templates go wrong.

If you wouldn’t say it out loud, don’t write it.

Instead of:

“We are a leading provider of innovative solutions…”

Try:

“I came across your work and thought it was interesting especially how your team handles…”

Your cold email should feel like a short, thoughtful message not a brochure. This matters even more when you’re new to prospecting or trying to build early business connections.

 

Personalization That Doesn’t Feel Forced

Personalization doesn’t mean stalking someone’s entire online presence.

It means showing awareness.

Good personalization examples:

  • Referencing a recent blog post or product update
  • Mentioning a shared industry or challenge
  • Acknowledging their role or team focus

Bad personalization:

  • Using their name 10 times
  • Fake compliments
  • Overly detailed references that feel creepy

A single genuine line is enough to show effort and effort leads to replies.

 

Keep the Body Short and Purposeful

Here’s a rule I learned the hard way:
If your cold email needs scrolling, it’s too long.

Aim for:

  • 3–5 short paragraphs
  • Plenty of white space
  • One clear idea

This applies whether you’re doing lead nurturing, reaching out for IT collaborations, or exploring client acquisition opportunities.

Busy people skim. Make skimming easy.

 

Ask One Clear, Low-Pressure Question

Your call to action shouldn’t feel like homework.

Avoid:

  • “Can we schedule a 30-minute call this week?”
  • “Please review the attached document and let me know”

Try:

  • “Would it make sense to talk?”
  • “Is this something you handle?”
  • “Open to a quick chat sometime?”

Low pressure = higher response rates.

Remember, a reply even a “not right now” means your cold email worked.

 

Follow-Ups: Where Most Replies Actually Happen

Here’s a secret most people don’t tell you:
Many replies come from follow-ups, not the first email.

A polite follow-up after 3–5 days can double your response rates.

Keep it simple:

“Just wanted to bump this in case it got buried.”

No guilt. No pressure. Just a reminder.

In IT and sales roles, consistent follow-ups are part of effective prospecting not desperation.

 

Treat Cold Email as a Skill, Not a Script

The best cold email templates are never truly “final.”

They evolve.

You test subject lines. You tweak phrasing. You notice what gets replies and what doesn’t. Over time, your emails start to feel more natural and people respond because they trust the tone.

This mindset is especially helpful if you’re exploring a career in IT, sales engineering, or technical consulting. Communication is just as important as technical skills.

 

Conclusion: Start Conversations, Not Campaigns

If there’s one thing I want you to remember, it’s this:

Cold emails work when they feel warm.

You don’t need tricks. You don’t need hype. You need clarity, honesty, and a bit of empathy for the person on the other side of the screen.

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