Update of D ID exclude service/location: Difference between revisions
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) m Text replacement - "[[Orphans in Centralized_data.accdb]]" to "Orphans in Centralized_data.accdb" |
||
| (6 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
This page documents | This page documents a proposed but abandoned move to a [[D_ID]] that no longer contains the [[Service/Location]]. | ||
{{LegacyContent | |||
|explanation= The reasons to do this are no longer valid. | |||
|content= | |||
== Background == | == Background == | ||
=== Rationale for doing this === | === Rationale for doing this === | ||
At some point, including the [[Service/Location]] in [[D_ID]] was the biggest cause of [[Orphans in Centralized_data.accdb]], and required special processes such as [[Changing D IDs]]. With everyone now entering fewer profiles and fewer [[Service Location]]s due to [[PatientFollow Project]], there should be much fewer problems caused by this, so this change is likely not worth the effort. | |||
==== Rationale for ''not'' doing this ==== | |||
This would be a fairly troublesome change for sending. | |||
Also, if there is an outstanding [[Instructions for requesting a batch of data from DSM | request]], changing the [[Service/Location]] can break the connection to the returned data when it is [[Instructions for importing a batch of DSM Data |imported]]. | Also, if there is an outstanding [[Instructions for requesting a batch of data from DSM | request]], changing the [[Service/Location]] can break the connection to the returned data when it is [[Instructions for importing a batch of DSM Data |imported]]. | ||
=== Considerations that it is possible to do this === | === Considerations that it is possible to do this === | ||
| Line 25: | Line 27: | ||
We have updated the [[Sending_Patients#What_happens_when_patients_are_sent|send functionality]] for this. | We have updated the [[Sending_Patients#What_happens_when_patients_are_sent|send functionality]] for this. | ||
We will either need to make the change contingent on start_date field or there will be [[Orphans in | We will either need to make the change contingent on start_date field or there will be [[Orphans in Centralized_data.accdb]]to clean up. | ||
Some steps required: | |||
* created Function make_D_ID | * created Function make_D_ID | ||
** '''Problem:''' If I use a function for this, then the way the delete queries work breaks with a non-specific ''#Error'' if a record has been deleted; Possible solutions: | ** '''Problem:''' If I use a function for this, then the way the delete queries work breaks with a non-specific ''#Error'' if a record has been deleted; Possible solutions: | ||
| Line 37: | Line 39: | ||
* I plan to have this function just generate the old style D_ID for now, and integrate it into all the sending spots. Then we can decide the start dttm after which we want to use the new format, and I just set that as a parameter in the function. | * I plan to have this function just generate the old style D_ID for now, and integrate it into all the sending spots. Then we can decide the start dttm after which we want to use the new format, and I just set that as a parameter in the function. | ||
=== Data use - no changes required === | === Data use - no changes required === | ||
| Line 47: | Line 47: | ||
The Tiss import process will need to be updated to use the new D_ID format based on start_date field. If this is done successfully, I '''''think''''' no further process change would be necessary. | The Tiss import process will need to be updated to use the new D_ID format based on start_date field. If this is done successfully, I '''''think''''' no further process change would be necessary. | ||
== Related articles == | == Related articles == | ||
{{Related Articles}} | {{Related Articles}} | ||
}} | |||