Object Reuse 2017 08 02

Poplin Object Reuse

Agenda

• Purpose (2 minutes)
• Discussion (55 minutes)
• Wrap-up (3 minutes)

Notes

• Should create an object repository
  • Similar to http://standardhealthrecord.org/shr/
  • Objects can be broken into categories for easy lookup
  • Service definitions can then simply reference object specification in object repository
  • If an extension is needed, the service definition itself should document additional fields, types, values, as specified in the service definition template
• Objects should have points of extension
  • Single element with data blob
  • Working group to review extensions and manage scope of variation to prevent unlimited object divergence

Action Items

• (MITRE) Create object repository as part of Poplin website
  • Will create an infrastructure of text files in GitHub that will allow WG members to update directly in GitHub using Markdown
  • Will hopefully have something to demonstrate this Friday
• (WG Members) Continue to work on service definitions as before. When object repository is ready, move object definitions from the service definitions into the object repository and add references to the service definition
• (WG Members) All objects should have an “extension” data blob field
• (WG Members) Once the object repository is available, if an object is needed for a service, first check the object repository to see if an existing object can be reused. If not, add the new object to the object repository.