Push cases from one PhenoTips instance to another

Description

As a clinician, I would like to be able to push a patient record from my local/institutional PhenoTips instance to another PhenoTips instance (such as PhenomeCentral). I would like to be able to choose what data gets pushed. I need a way to keep the pushed data up-to-date with changes I make to my record.

Activity

Show:
Orion Buske
July 28, 2015, 9:07 PM

<p>These fields should be supported by the push API and JSON import/export more generally, since pushing is not always to PhenomeCentral. PhenomeCentral, however, should be configured to disallow pushing these specific fields to it (which it already is, I believe). </p>

CourtneyHum
July 28, 2015, 5:12 PM

<p><a href=https://genomequebec.mcgill.ca/jira/secure/ViewProfile.jspa?name=Orion.Buske class=user-hover rel=Orion.Buske>Orion Buske</a> I think users should be permitted to push almost every field, so the specific sub-tasks listed up above are not exhaustive. From the top of my head, I think that the only fields that should not be permitted to be pushed are:</p>

<ul class=alternate type=square>
<li>Name</li>
<li>DOB: day</li>
<li>DOD: day</li>
<li>Name, DOB:day and DOD:day for family members on pedigree</li>
<li>Medical reports</li>
<li>Free text boxes like indication for referral, comments in prenatal history and medical and developmental history need to be reviewed by the user before they are pushed with a warning not to allow PII to go through.</li>
<li>Images are debatable, again user need to be required to review before pushing</li>
</ul>

Orion Buske
July 23, 2015, 10:17 PM

<p>One complexity of this, which <a href=https://genomequebec.mcgill.ca/jira/secure/ViewProfile.jspa?name=Courtney.Hum class=user-hover rel=Courtney.Hum>Courtney Hum</a> brought up, is that external identifiers may be inappropriate to push (e.g. MRNs). However, if they are not pushed, then there is currently no good way to figure out which record represent the same patient. For example, if I push several patients from PhenoTips A to PhenomeCentral, and then get notified a match in PhenomeCentral involving one of my patients, how do I quickly find out which patient this is? One potential solution would be to show the provenance of pushed patients on the patient record.</p>

<p>For example, if a patient was pushed from PhenoTips A to PhenomeCentral, the patient record on PhenomeCentral would show:</p>
<div class=panel style=border-width: 1px;><div class=panelContent>
<p>Pushed from PhenoTips A - P0000123</p>
</div></div>
<p>and the patient record on PhenoTips A would show:</p>
<div class=panel style=border-width: 1px;><div class=panelContent>
<p>Pushed to PhenomeCentral - P0015824</p>
</div></div>
<p>These could even be stored as additional external identifiers, one for each push destination, to allow easy filtering (<a href=https://genomequebec.mcgill.ca/jira/browse/PT-42 title=Multiple external IDs per patient class=issue-link data-issue-key=PT-42>PT-42</a>).</p>

Orion Buske
July 21, 2015, 3:58 PM

<p>One potential way of keeping the original and pushed patient in sync is to disable editing of the new record at the destination PhenoTips instance. This makes sense for PhenomeCentral, but might not make sense for other use cases. Should we allow each record to change and then just perform a merge or overwrite on the next push? Should we allow pushing back changes to the original instance (might not be possible from PhenomeCentral)?</p>

Fixed

Assignee

Unassigned

Reporter

Orion Buske

Labels

None

Epic/Theme

None

Introduced In

None

Updated In

None

Epic Name

Push