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

MWL Feed from HL7 Order Message: optionally extract Scheduled Protocol Code from OBR-4 components 1-3, instead from OBR-4 components 4-6 #579

Closed
gunterze opened this issue Mar 13, 2017 · 0 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@gunterze
Copy link
Member

gunterze commented Mar 13, 2017

Configurable on Archive Device level or Archive HL7 Application level by Parameters

Name Description LDAP attribute
HL7 Schedule Protocol Code in Order Specifies location of Scheduled Protocol Code in received HL7 Order message. Enumerated values: OBR_4_1, OBR_4_4. If absent, OBR_4_4 will be applied. hl7ScheduledProtocolCodeInOrder

Reference : DSS Mappings of OBR Segment

@gunterze gunterze added the enhancement New feature or request label Mar 13, 2017
@gunterze gunterze added this to the 5.9.4 milestone Mar 13, 2017
gunterze added a commit that referenced this issue Mar 13, 2017
@gunterze gunterze changed the title MWL Feed from HL7 Order Message: configurable location of Scheduled Protocol Code in OBR-4 MWL Feed from HL7 Order Message: optionally extract of Scheduled Protocol Code from OBR-4 components 1-3, instead from OBR-4 components 4-6 Mar 13, 2017
@gunterze gunterze changed the title MWL Feed from HL7 Order Message: optionally extract of Scheduled Protocol Code from OBR-4 components 1-3, instead from OBR-4 components 4-6 MWL Feed from HL7 Order Message: optionally extract Scheduled Protocol Code from OBR-4 components 1-3, instead from OBR-4 components 4-6 Mar 13, 2017
gunterze added a commit that referenced this issue Mar 13, 2017
…l Code from OBR-4 components 1-3, instead from OBR-4 components 4-6 #579
vrindanayak added a commit to dcm4che/dcm4chee-arc-cs that referenced this issue Mar 14, 2017
…ionally extract Scheduled Protocol Code from OBR-4 components 1-3, instead from OBR-4 components 4-6
gunterze added a commit to dcm4che-dockerfiles/slapd-dcm4chee that referenced this issue Mar 15, 2017
…l Code from OBR-4 components 1-3, instead from OBR-4 components 4-6 dcm4che/dcm4chee-arc-light#579
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants