Stream: fmg
Topic: R4 Product Agenda
Grahame Grieve (Apr 19 2017 at 21:17):
This is my proposed list for discussion:
Grahame Grieve (Apr 19 2017 at 21:17):
Product Directors R4 Agenda:
- Normative: push to normative for
- Foundation / API / XML / JSON / Bundle / OperationOutcome
- Terminology Service (ValueSet / CodeSystem / ExpansionProfile)
- StructureDefinition / CapabilityStatement
- Patient / RelatedPerson / Practitioner / Organization / ?Endpoint
-
position a core set of clinical resources ('health base'?) for normative in R5 (or Observation | AllergyIntolerance | MedicationStatement normative for R4?)
-
JSON: use manifest for extensions, parameters resource (see forthcoming blog post)
- RDF: more ontology bindings + resolve status of JSON-LD
- Data Analytics: support for a bulk data analysis bridge format (parquet?)
- API: better control over retrieving graphs, and value added query (tabular format?)
- Patterns: change W5 to a pattern (logical model) / tie patterns to ontology / use of patterns to drive more consistency and how to do this without decreasing quality
- Services: more services (conformance, registry, personal health summary? / etc?)
- Deployment: get a clear standards path for smart on fhir / cds-hooks (and alignment with heart)
- FM: better alignment between FM and the rest of FHIR
Note: this list anticipates that normal standards development process occur, and the content as a whole is maintained.
This is an indication of where particular focus will be applied
David Hay (Apr 25 2017 at 19:41):
From @Lenel James : • For STU4 objectives, add greater guidance and recommended formatting for FHIR Profiles “versions” and FHIR Bundle “identifiers”, as the basis for operations and production exchange between providers, payer and HIE during software upgrades and software revisions that will change profiles and bundle.
Grahame Grieve (Apr 25 2017 at 21:01):
not against adding more advice, but that doesn't sound like a product agenda
Last updated: Apr 12 2022 at 19:14 UTC
