Add EHR_STATUS class to EHR package
Raise CR
Analysis
Resolution
Raise CR
Analysis
Resolution
Description
Activity
Show:
Thomas Beale
updated the ReporterOctober 7, 2011 at 7:10 AMUser
Heath Frankel
Thomas Beale
updated the WorkflowAugust 11, 2008 at 10:18 PMCopy of ARB CR
ARB CR
Thomas Beale
updated the WorkflowAugust 11, 2008 at 10:14 PMARB CR
Copy of ARB CR
openEHR admin
updated the WorkflowAugust 11, 2008 at 10:05 PMCopy of ARB CR
ARB CR
openEHR admin
updated the WorkflowAugust 11, 2008 at 9:58 PMARB CR
Copy of ARB CR
openEHR admin
updated the WorkflowMarch 12, 2008 at 4:21 AMCR
ARB CR
Former user
created the IssueJanuary 4, 2006 at 12:00 AMFixed
Assignee
Reporter
Heath Frankel
Heath FrankelPriority
Created January 4, 2006 at 12:00 AM
Updated October 7, 2011 at 7:10 AM
Resolved October 7, 2011 at 7:10 AM
The EHR class includes subject and time_created. But there is a need for
an ehr_id distinct from the subject id. All EHRs have their own id, but
in reality, two EHRs could have the same subject id, due to errors that
occur in real systems, data entry etc. Also, subject id needs to be
versioned (sometimes it turns out that the data of the EHR is correct, but
the subject id has to be changed, e.g. the current one is a duplicate for
the same patient and is being dropped).
Aloso, currently there is no clear place to store EHR management data e.g.
active/inactive status
merged status
patient inactive / not under care (therefore cancel notifications)
Creating a standardised versioned object for this purpose would allow
EHR-level atributes to be versioned, and openEHR software to interoperate
with data in different EHRs.