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.

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

v2.7: Missing messages #131

Closed
jgarciaroca opened this issue Aug 7, 2024 · 2 comments
Closed

v2.7: Missing messages #131

jgarciaroca opened this issue Aug 7, 2024 · 2 comments

Comments

@jgarciaroca
Copy link
Contributor

List of missing messages: ADT_A04, ADT_A07, ADT_A08, ADT_A10, ADT_A11, ADT_A13, ADT_A14, ADT_A22, ADT_A23, ADT_A25, ADT_A26, ADT_A27, ADT_A28, ADT_A29, ADT_A31, ADT_A32, ADT_A33, ADT_A40, ADT_A41, ADT_A42, ADT_A47, ADT_A49, ADT_A51, ADT_A53, ADT_A55, MFN_M14, PMU_B02, PMU_B05, PMU_B06

More might be missing, i just detected those doing a sequential search of existing message gaps.

jgarciaroca added a commit to jgarciaroca/hl7apy that referenced this issue Aug 7, 2024
List of messages: ADT_A04, ADT_A07, ADT_A08, ADT_A10, ADT_A11, ADT_A13, ADT_A14, ADT_A22, ADT_A23, ADT_A25, ADT_A26, ADT_A27, ADT_A28, ADT_A29, ADT_A31, ADT_A32, ADT_A33, ADT_A40, ADT_A41, ADT_A42, ADT_A47, ADT_A49, ADT_A51, ADT_A53, ADT_A55 MFN_M14, PMU_B02, PMU_B05, PMU_B06, PPR_PC2, PPR_PPC3
@svituz
Copy link
Member

svituz commented Jan 7, 2025

Hi @jgarciaroca, I read the documentation, and all the ADT messages you pointed out are not actually valid.
The A04 event must be used with the trigger event ADT_A01 and the A08 event as well. Similarly, the A07 event should be used with the ADT_A06 trigger event, and so on. Same thing for PMU trigger events (B05 should be used with PMU_B01, B05 and B06 with PMU_B04).
Regarding the M14 event for MFN, that should be used with Znn messages which I admit I wasn't aware of. The support for this kind of Z trigger events should be handled in another way probably.

@svituz svituz closed this as completed Jan 7, 2025
@jgarciaroca
Copy link
Contributor Author

You are right. When i created the PR i didn't realized that the test messages i was trying to parse where being send wrong. the MSH.9 received was pointing to "ADT^A04^ADT_A04" instead of "ADT^A04^ADT_A01", so the parser couldn't parse that message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants