Message-ID: <127809941.264.1432995814753.JavaMail.confluence@gw81> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_263_1670769559.1432995814717" ------=_Part_263_1670769559.1432995814717 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-172= 2=20||=20||Observations for numeric= concepts should also support exceptional values=20|
|TRUNK-199= 1=20||=20||Support external master = registries of Patient, Location, Provider, Concept and other metadata ==20|
|TRUNK-369= 7=20||=20||Add a location attribute= to a Provider=20|
|TRUNK-413<= /a>=20||=20||Implement the Structured = Numeric datatype=20|
|TRUNK-367= 2=20||=20||Distribute the OpenMRS W= AR without bundled modules, while making it easy to add that bundle = td>=20|
|TRUNK-315= 8=20||=20||Add more control over fl= ush mode=20|
|TRUNK-372= 6=20||=20||Standardize codebase on = maven 3=20|
|TRUNK-364= 7=20||=20||Should allow a form sche= ma to be shared by more than one form entry module=20|
|TRUNK-424= 7=20||=20||Allow any metadata objec= t to be marked as required and thus not removable=20|
|TRUNK-425= 2=20||=20||Date fields are stored p= recise to the second in the DB, and MySQL 5.6 rounds milliseconds instead o= f truncating them=20|
|TRUNK-274= 0=20||=20||refactor several get con= cept routines to new concept name selection criteria=20|
|TRUNK-253= 5=20||=20||Using merge in service l= ayer=20|
|TRUNK-231= 1=20||=20||Add patient.person_id at= tribute to data model=20|
|TRUNK-231= 0=20||=20||Add getPerson() method t= o Patient as preferred method of getting person=20|
|TRUNK-228= 4=20||=20||Common tagging mechanism= for openmrs objects=20|
|TRUNK-187= 2=20||=20||Add a global property se= rvice which supports more robust registration and handling of global proper= ties=20|
The notes/minutes for each call are available at notes.openmrs.org/Design-Forum-YYYY-MM-DD=20