Uploaded image for project: 'OpenMRS Core'
  1. OpenMRS Core
  2. TRUNK-5629

org/openmrs/hl7/handler/ORUR01Handler.java

    XMLWordPrintable

Details

    • Undetermined

    Description

      TODO: ideally, we would branch or alter our behavior based on the

      Location:

      https://github.com/openmrs/openmrs-core/blob/2.2.0/api/src/main/java/org/openmrs/hl7/handler/ORUR01Handler.java#L182

       

      // TODO: check version, etc.

      Location:

      https://github.com/openmrs/openmrs-core/blob/2.2.0/api/src/main/java/org/openmrs/hl7/handler/ORUR01Handler.java#L488

       

      TODO: support RP (report), SN (structured numeric)

      Location:

      https://github.com/openmrs/openmrs-core/blob/2.2.0/api/src/main/java/org/openmrs/hl7/handler/ORUR01Handler.java#L827

       

      TODO: resolve encounter type from MSH data - do we need PV1 too?

      Location:

      https://github.com/openmrs/openmrs-core/blob/2.2.0/api/src/main/java/org/openmrs/hl7/handler/ORUR01Handler.java#L1176

       

      TODO: Debug (and use) methods in HL7Util instead

      Location:

      https://github.com/openmrs/openmrs-core/blob/2.2.0/api/src/main/java/org/openmrs/hl7/handler/ORUR01Handler.java#L1191

       

      value is a proposed concept, create a ConceptProposal instead of an Obs for this observation at this point if componentSeparator (^) is in text, we'll only use the text before that delimiter!

      Location:

      https://github.com/openmrs/openmrs-core/blob/2.2.0/api/src/main/java/org/openmrs/hl7/handler/ORUR01Handler.java#L1218

       

      ideally, we would branch or alter our behavior based on the sending application.

      Location:

      https://github.com/openmrs/openmrs-core/blob/2.2.0/api/src/main/java/org/openmrs/hl7/handler/ORUR01Handler.java#L182

      Gliffy Diagrams

        Attachments

          Issue Links

            relates to

            Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. TRUNK-324 Go through the TODO items code and create tickets out of them

            • Should - Issue should be completed for its milestone; however, will not delay the milestone.
            • Ready for Work

            Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. TRUNK-6087 COPY: Go through the TODO items code and create tickets out of them

            • Should - Issue should be completed for its milestone; however, will not delay the milestone.
            • Needs Assessment

            Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. TRUNK-6108 COPY: Go through the TODO items code and create tickets out of them

            • Should - Issue should be completed for its milestone; however, will not delay the milestone.
            • Needs Assessment

            Activity

              People

                Unassigned Unassigned
                isaaclin isaac lin
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: