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

org/openmrs/hl7/impl/HL7ServiceImpl.java

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Needs Assessment
    • Priority: TBD
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Complexity:
      Undetermined
    • Development:

      Description

      TODO: Get rid of hack that allows first component to be an integer location.location_id

      Location:

      https://github.com/openmrs/openmrs-core/blob/2.2.0/api/src/main/java/org/openmrs/hl7/impl/HL7ServiceImpl.java#L535

       

      TODO: Properly handle assigning authority. If specified it's currently treated as PatientIdentifierType.name

      Location:

      https://github.com/openmrs/openmrs-core/blob/2.2.0/api/src/main/java/org/openmrs/hl7/impl/HL7ServiceImpl.java#L595

       

      TODO: Throw exceptions instead of returning null in some cases

      Location:

      https://github.com/openmrs/openmrs-core/blob/2.2.0/api/src/main/java/org/openmrs/hl7/impl/HL7ServiceImpl.java#L597

       

      TODO other potential identifying characteristics in PID we could use to identify the patient

      Location:

      https://github.com/openmrs/openmrs-core/blob/2.2.0/api/src/main/java/org/openmrs/hl7/impl/HL7ServiceImpl.java#L604

       

      TODO if 1st component is blank, check 2nd and 3rd of assigning authority

      Location:

      https://github.com/openmrs/openmrs-core/blob/2.2.0/api/src/main/java/org/openmrs/hl7/impl/HL7ServiceImpl.java#L610

       

      TODO: generalize this for use with both PID and NK1 segments

      Location:

      https://github.com/openmrs/openmrs-core/blob/2.2.0/api/src/main/java/org/openmrs/hl7/impl/HL7ServiceImpl.java#L882

        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

              Activity

                People

                Assignee:
                Unassigned Unassigned
                Reporter:
                isaaclin isaac lin
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                  Dates

                  Created:
                  Updated: