TRUNK-257 Add Feature to enable moving Encounter Data to a different pat... #314
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| /** | ||
| * Mapping Class between Encounters and Providers which allows many to many relationship. | ||
| * | ||
| * @since 1.9 | ||
| */ | ||
| public class EncounterProvider extends BaseOpenmrsData { | ||
| public class EncounterProvider extends BaseOpenmrsData implements Serializable { |
There was a problem hiding this comment.
Good catch! I sometimes think BaseOpenmrsObject should be doing this.
ghost
assigned 
| // void visit if voided encounter is the only one | ||
| Visit visit = encounter.getVisit(); | ||
| if (visit != null && visit.getEncounters().size() == 1) { | ||
| Context.getVisitService().voidVisit(visit, "Visit don't contain non-voided encounters"); |
There was a problem hiding this comment.
Change "don't" to "does not"
… patient TRUNK-3980: Add back button support for patient search page TRUNK-257 Add Feature to enable moving Encounter Data to a different patient TRUNK-257 Add Feature to enable moving Encounter Data to a different patient TRUNK-257 Add Feature to enable moving Encounter Data to a different patient TRUNK-257: Add Feature to enable moving Encounter Data to a different patient - service API methods TRUNK-257 Add Feature to enable moving Encounter Data to a different patient TRUNK-257 Add Feature to enable moving Encounter Data to a different patient TRUNK-257 Add Feature to enable moving Encounter Data to a different patient TRUNK-257: Add Feature to enable moving Encounter Data to a different patient - service API methods TRUNK-3943: Support data preserve on browser back button in concept search page Manage preferred status for PersonName, PersonAddress and PatientIdentifier in the API - TRUNK-2200 Follow up to set the preferred or fully specified name for a concept list item - TRUK-3232 Manage preferred status for PersonName, PersonAddress and PatientIdentifier in the API - TRUNK-2200 Taken care of patient identifier and also updated savePatient - TRUNK-2200 get folder for module web files programatically - TRUNK-1589 Made some changes - TRUNK-1589 Made more changes to the tests - TRUNK-1589 Applied auto format changes - TRUNK-1589 NonUniqueObjectException: a different object with the same identifier value was already associated with the session: [org.openmrs.Patient#] - TRUNK-3728 Applying auto format changes - TRUNK-3728 TRUNK-3979: LoggingAdvice should also log which user is performing an action when an error occurs Null check and taking systemId if username is empty User null check Fix of code duplication Search for patient by identifier fails when identifier is made of only letters - TRUNK-3822 Follow up - TRUNK-3822 Follow up to fix some issues - TRUNK-3822 Fixed patientService.getPatientCount method - TRUNK-3822 Follow up to fix failing unit test - TRUNK-3822 Apply auto format changes and fixed HibernateEncounterDAO - TRUNK-3822 OpenMRS crashes irrecoverably if particular errors occur during module loading - TRUNK-2850 TRUNK-3992: PersonByNameComparator should be case-insensitive TRUNK-3206: Added test methods for HibernatePatientDAO.HibernatePatientDAO.getPatientIdentifierTypes Removing unused message for: Force password change page help text should reflect security global properties - TRUNK-1868 Changing the number of characters from 49 to 50 as expected in PersonNameValidatorTest for: Add regex validation to PersonNameValidator - TRUNK-2616 TRUNK-257 Add Feature to enable moving Encounter Data to a different patient TRUNK-257 Add Feature to enable moving Encounter Data to a different patient TRUNK-257 Add Feature to enable moving Encounter Data to a different patient TRUNK-257: Add Feature to enable moving Encounter Data to a different patient - service API methods TRUNK-257 Add Feature to enable moving Encounter Data to a different patient TRUNK-257 Add Feature to enable moving Encounter Data to a different patient TRUNK-257 Add Feature to enable moving Encounter Data to a different patient TRUNK-257: Add Feature to enable moving Encounter Data to a different patient - service API methods TRUNK-257: Add Feature to enable moving Encounter Data to a different patient - service API methods TRUNK-257: Add Feature to enable moving Encounter Data to a different patient - user interface TRUNK-257: Add Feature to enable moving Encounter Data to a different patient - user interface TRUNK-257: Add Feature to enable moving Encounter Data to a different patient - user interface TRUNK-257: Add Feature to enable moving Encounter Data to a different patient - user interface TRUNK-257: Add Feature to enable moving Encounter Data to a different patient - user interface TRUNK-257: Add Feature to enable moving Encounter Data to a different patient TRUNK-257: Add Feature to enable moving Encounter Data to a different patient TRUNK-257: Add Feature to enable moving Encounter Data to a different patient TRUNK-257: Add Feature to enable moving Encounter Data to a different patient TRUNK-257: Add Feature to enable moving Encounter Data to a different patient TRUNK-257: Add Feature to enable moving Encounter Data to a different patient TRUNK-257: Add Feature to enable moving Encounter Data to a different patient TRUNK-257: Add Feature to enable moving Encounter Data to a different patient - user interface TRUNK-257 - rebase with upstrem master TRUNK-257 - rebase with upstrem master TRUNK-257 - rebase with upstrem master - remove *.orig files TRUNK-257 - merge with upstream/master TRUNK-257 - fix junit tests remove not my changes remove unecessary changes TRUNK-257 - review changes v.1 TRUNK-257 - review changes v.2 TRUNK-257 - review changes v.3
|
Closing because author abandoned it. |
RandilaP
pushed a commit
to RandilaP/openmrs-core
that referenced
this pull request
Jul 31, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
initial review, work on this ticket is not finished - service API layer only