Downloads:

51

Downloads of v 2.5.3:

24

Last Update:

09 Sep 2020

Package Maintainer(s):

Software Author(s):

  • Carsten Rambow

Tags:

hl7inspector hl7 ihe connectathon healthcare integration

HL7 Inspector

2.5.3 | Updated: 09 Sep 2020

Downloads:

51

Downloads of v 2.5.3:

24

Maintainer(s):

Software Author(s):

  • Carsten Rambow

HL7 Inspector 2.5.3

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install HL7 Inspector, run the following command from the command line or from PowerShell:

>

To upgrade HL7 Inspector, run the following command from the command line or from PowerShell:

>

To uninstall HL7 Inspector, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade hl7inspector -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade hl7inspector -y --source="'STEP 3 URL'"
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Ensure hl7inspector installed
  win_chocolatey:
    name: hl7inspector
    state: present
    version: 2.5.3
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'hl7inspector' do
  action    :install
  version  '2.5.3'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: hl7inspector,
    Version: 2.5.3,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller hl7inspector
{
   Name     = 'hl7inspector'
   Ensure   = 'Present'
   Version  = '2.5.3'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'hl7inspector':
  provider => 'chocolatey',
  ensure   => '2.5.3',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install hl7inspector version="2.5.3" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.

  • Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
  • Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
  • Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.

Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.

This package was approved by moderator gep13 on 10 Sep 2020.

Description

The HL7 Inspector is a useful open source tool for integration the HL7 Version 2 in a health care environmental. It will help you to minimize the time for tuning the HL7 communication between systems such as HIS and RIS by analyzing and validating HL7 messages. ###Features * Parsing of HL7 messages * Sending/receiving of messages on IP sockets * Reading of HL7 messages from (compressed) text/log files * Simple message editor * Full Unicode support * ...and many more For a complete list please go to https://bitbucket.org/crambow/hl7inspector/src/master/release-notes.md


tools\chocolateyinstall.ps1
#Install-VirtualPackage 'hl7inspector.install'

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
HL7 Inspector 2.5.0 17 Wednesday, September 2, 2020 Approved
Discussion for the HL7 Inspector Package

Ground Rules:

  • This discussion is only about HL7 Inspector and the HL7 Inspector package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or HL7 Inspector, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus