List goals for this meeting (e.g., Set design priorities for FY19):
previous meeting:
Item | Presenter | Notes | |
---|---|---|---|
5 min | Opening | USEFUL Jira RESOURCE: CRs I have not accepted. | |
15 min | SEC governance:
| ||
15 min | PR / CR processing - plan, progress - need to increase rate of resolutions | ||
15 min | Conformance framework - progress; call for participation | Erik Sundvall - don't forget the secret data sets for procurement to prevent fixed response faking Seref Arikan (Personal) - need to find out current regression / passing situation - probably not 100% | |
15 min | TDS / TDD - progress report |
| |
10 mins | Endpoint for committing persistent composition | EDIT: there is now a wiki page for this topic and a Discourse discussion. Need an atomic operation of committing a certain COMP iff doesn’t already exist (e.g. no meds list yet), i.e. can’t create accidental duplicates; problem of race condition of N clients trying to create a Meds list; could be done by checking a business rule settable in a given deployment that limits some template xyz to only one instance. Where are the rule(s) encoded? Heath Frankel (Unlicensed) What about when the Composition is part of a multi-Composition Contribution? Potentially this needs to be managed in the back-end site-level config / rules. Seref Arikan (Personal) one approach for dedicated API for Meds list. FHIR… Erik Sundvall endpoint ‘black list’ - special template ids? Should be a customer question | |
Next SEC call | |||
Outstanding topics:
| |||
Outstanding topics: |
Add action items to close the loop on open questions or discussion topics: