Change Description:
First-nations communities utilize a "status number" or "band number" to identify the tribe or family that an individual is from. Reference from Health Canada website below.
Health Canada - First Nations & Inuit Health - Client Identification
http://www.hc-sc.gc.ca/fniah-spnia/nihb-ssna/provide-fournir/client-beneficiaire-eng.php
OSCAR offers "status number" functionality by enabling the following setting in the properties file:
EXTRA_DEMO_FIELDS=vnativefield
One such example is the demographic page.
This change is to extend the "status number" field to the search and the prescriptions.
OSCAR Interaction points:
Search
Prescriptions
Integration risks:
* None.
Risk if not incorporated
* Status number functionality will not be available in the search or prescriptions area.
Minimum testing requirements/process:
* Requirements will be tested as per attached document.
Training requirements to support changes
* None
Time Estimate
* None - will be completed by Trimara.
Diff:
Diff:
Is there benefit in generalizing the request?
I imagine this could be useful for other numbers (like military id, drug plan account maybe)
DemographicExt has been used in the past.
Try adding
EXTRA_DEMO_FIELDS=vnativefields
to the properties file. This will show more fields in the master demographic.
although the data won't show up in OSCAR 15 patient details screen
does this mean that OSCAR15 will not be supporting the display that exists
already with:
EXTRA_DEMO_FIELDS=vnativefields
?
On Wed, Sep 30, 2015 at 10:02 AM, Marc Dumontier hexbinary@users.sf.net
wrote:
--
+
Thom Luxford, B.HK B.CS
Project Manager IT
bCMDit Services Ltd.
2411-160th Street, Suite 250
Surrey, BC V3Z 0C8 Canada
(778) 370-3030
Related
Feature Requests: #1267
They show up just fine in the classic interface.
Dennis Warren
Consultant
Colcamex Resources
dwarren@colcamex.com
778.386.9264
Related
Feature Requests: #1267
Hi Marc. The change needs to go into 12 (in our pilot branch). As per process, we would commit to 15 as well. If you want the value stored in the DemographicExt table so that we don't have to modify the demographic table, I don't see an issue with that. Do we have authorization to move forward?
yes, use demographicExt
my understanding is you will commit to your 12.1 pilot branch + master..not RELEASE_12_1
Correct. Thanks Marc.
EXTRA_DEMO_FIELDS not currently in R15
Diff:
Diff:
Updated description to indicate that we are simply extending existing functionality.