[go: nahoru, domu]
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[IDEA] Automatically hash outgoing messages #5494

Closed
pladesma opened this issue Oct 24, 2022 · 1 comment
Closed

[IDEA] Automatically hash outgoing messages #5494

pladesma opened this issue Oct 24, 2022 · 1 comment
Labels
enhancement New feature or request Fix-Commited Issue fixed and will be available in milestone Internal-Issue-Created An issue has been created in NextGen's internal issue tracker RS-9302
Milestone
4.2.0

Comments

@pladesma
Copy link
Collaborator

Automatically generate a SHA-256 hash for each outgoing message. Make the hash available as a velocity variable ${HASH} in each Destination connector. It should also be available as a drag-and-drop variable Message Hash from the Destination Mappings list.

This feature would make it simpler to implement a way of ensuring message integrity, meaning ensuring that the message hasn't been altered in transit.
@pladesma pladesma added enhancement New feature or request Fix-Commited Issue fixed and will be available in milestone Internal-Issue-Created An issue has been created in NextGen's internal issue tracker RS-9302 labels Oct 24, 2022
@pladesma pladesma added this to the 4.2.0 milestone Oct 24, 2022
@jonbartels
Copy link
Contributor

Would this hash be computed on the entire message or a configurable portion of the message?

I ask because hashing for validation is one thing. That would be the hash of the full content.

A related use case is message deduplication - So you might have HL7 messages where an EMR (cough Epic cough) spams out ADTs where only the MSH segment differs but all other data is the same.

Is this case related to #5476 ?

@pladesma pladesma closed this as completed Dec 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request Fix-Commited Issue fixed and will be available in milestone Internal-Issue-Created An issue has been created in NextGen's internal issue tracker RS-9302
Projects
None yet
Milestone
4.2.0
Development

No branches or pull requests
2 participants
@pladesma @jonbartels