Update of D ID exclude service/location: Difference between revisions

Line 2:

== Background ==

=== Rationale for doing this ===

Including the [[Service/Location]] in [[D_ID]] is the biggest cause of [[Orphans in Centralized data.mdb]], and requires special processes such as [[Changing D IDs]]. So, we will remove this field from generating the D_ID.

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]].

==== Rationale for ''not'' doing this ====

{{Discuss |

This would be a fairly troublesome change for sending. With everyone now entering fewer profiles and fewer [[Service Locations]] due to [[PatientFollow Project]], there should be much fewer problems caused by this. So we should review if this is still a thing we want to do right now. I will consider this on hold unless someone tells me we should still do it. [[User:Ttenbergen|Ttenbergen]] 11:22, 2020 December 3 (CST)

}}

=== Considerations that it is possible to do this ===

When we first set up [[D_ID]] it consisted of the [[Pat_ID]] and the [[Service/Location]]. For reasons explained in [[Update of D ID to include a laptop identifier#Background]] we added the [[Laptop identifier]] to the [[D_ID]]. The [[D_ID]] now consists of three components: [[Laptop identifier]], [[Service/Location]] and [[Pat_ID]].

[[Pat_ID]]s used to be inconsistently unique per [[Service/Location]] or per [[Laptop identifier]], but as part of [[Facilitated Management of Serial numbers]] we unified this to use a single pool of [[Pat_ID]]s per [[Laptop identifier]].

As a result, it turns out that [[Laptop identifier]] and [[Pat_ID]] are now sufficient to guarantee a unique [[D_ID~~]].~~

As a result, it turns out that [[Laptop identifier]] and [[Pat_ID]] are now sufficient to guarantee a unique [[D_ID]].

Including the [[Service/Location]] in [[D_ID]] is the biggest cause of [[Orphans in Centralized data.mdb]], and requires special processes such as [[Changing D IDs]]. So, we will remove this field from generating the D_ID.

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]].

== Implementation ==

@@ Line 2: / Line 2: @@
 == Background ==
+=== Rationale for doing this ===
+Including the [[Service/Location]] in [[D_ID]] is the biggest cause of [[Orphans in Centralized data.mdb]], and requires special processes such as [[Changing D IDs]]. So, we will remove this field from generating the D_ID.
+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]].
+==== Rationale for ''not'' doing this ====
+{{Discuss |
+This would be a fairly troublesome change for sending. With everyone now entering fewer profiles and fewer [[Service Locations]] due to [[PatientFollow Project]], there should be much fewer problems caused by this. So we should review if this is still a thing we want to do right now. I  will consider this on hold unless someone tells me we should still do it. [[User:Ttenbergen|Ttenbergen]] 11:22, 2020 December 3 (CST)
+}}
+=== Considerations that it is possible to do this ===
 When we first set up [[D_ID]] it consisted of the [[Pat_ID]] and the [[Service/Location]]. For reasons explained in [[Update of D ID to include a laptop identifier#Background]] we added the [[Laptop identifier]] to the [[D_ID]]. The [[D_ID]] now consists of three components: [[Laptop identifier]], [[Service/Location]] and [[Pat_ID]].
 [[Pat_ID]]s used to be inconsistently unique per [[Service/Location]] or per [[Laptop identifier]], but as part of [[Facilitated Management of Serial numbers]] we unified this to use a single pool of [[Pat_ID]]s per [[Laptop identifier]].
 As a result, it turns out that [[Laptop identifier]] and [[Pat_ID]] are now sufficient to guarantee a unique [[D_ID]].
-Including the [[Service/Location]] in [[D_ID]] is the biggest cause of [[Orphans in Centralized data.mdb]], and requires special processes such as [[Changing D IDs]]. So, we will remove this field from generating the D_ID.
-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]].
 == Implementation ==