Message-ID: <745215192.40680.1427724628228.JavaMail.confluence@gw81> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_40679_470560925.1427724628209" ------=_Part_40679_470560925.1427724628209 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The OpenMRS Design Forums are one-hour calls twice each week for the pur= pose of discussing any design-related issues within the OpenMRS Community. = The calls are routinely attended by experienced developers and clinic= al informatics specialists. The design call is appropriate at several= stages of design:
Mondays 4:00pm-5:00pm UTC (excluding holidays). &n= bsp;Not in the UTC timezone? See t= he event in your timezone.
Wednesdays from 2:00pm-3:00pm US/Eastern (excludin= g holidays, changing with daylight saving time). Not in the US/Easter= n timezone? See the e= vent in your timezone.
Topics for the design call are chosen in the following order:
If you are in that third category and have a bit of work that you would = like to discuss the design as it pertains to OpenMRS, do three things:
If no specific design topic has been requested on the mailing list, we w= ill draw topics from JIRA tickets labeled with "design-review". T= hese are visualized and sorted on this JIRA dashboard. In order to add a ticket to this lis= t, just add the label "design-review" to the ticket. (In th= e past we tried to draw discussion topics from the JIRA "Design Review= " status but found that most tickets in that state = need someone to do the legwork of design, they don't particularly need a te= am discussion. Now we look to tickets that have manually been tagged for di= scussion).
|TRUNK-1722=20||=20||Observations for numeric concepts should = also support exceptional values=20|
|TRUNK-1991=20||=20||Support external master registries of Pat= ient, Location, Provider, Concept and other metadata=20|
|TRUNK-3697=20||=20||Add a location attribute to a Provider=20|
|TRUNK-413=20||=20||Implement the Structured Numeric datatype<= /a>=20|
|TRUNK-3672=20||=20||Distribute the OpenMRS WAR without bundle= d modules, while making it easy to add that bundle=20|
|TRUNK-3158=20||=20||Add more control over flush mode=20|
|TRUNK-4252=20||=20||Date fields are stored precise to the sec= ond in the DB, and MySQL 5.6 rounds milliseconds instead of truncating them==20|
|TRUNK-4247=20||=20||Allow any metadata object to be marked as= required and thus not removable=20|
|TRUNK-3726=20||=20||Standardize codebase on maven 3= =20|
|TRUNK-3647=20||=20||Should allow a form schema to be shared b= y more than one form entry module=20|
|TRUNK-2740=20||=20||refactor several get concept routines to = new concept name selection criteria=20|
|TRUNK-2535=20||=20||Using merge in service layer=20|
|TRUNK-2310=20||=20||Add getPerson() method to Patient as pref= erred method of getting person=20|
|TRUNK-2311=20||=20||Add patient.person_id attribute to data m= odel=20|
|TRUNK-2284=20||=20||Common tagging mechanism for openmrs obje= cts=20|
|TRUNK-1872=20||=20||Add a global property service which suppo= rts more robust registration and handling of global properties=20|
The notes/minutes for each call are available at notes.openmrs.org/Design-Forum-YYYY-MM-DD=20