- -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 blog post) (note that discussion on this didn’t go very well – probably will be dropped)
- -RDF: more ontology bindings + resolve status of JSON-LD
- Data Analytics: support for a bulk data analysis bridge format (Apache Parquet?)
- -API: better control over retrieving graphs, and value added query support (tabular format?)
- -Patterns: change the W5 framework to a pattern (logical model), tie the patterns to ontology, and use of patterns to drive more consistency (and how to do this without decreasing quality)
- -Services: more services. Candidates: conformance, registry, personal health summary?, etc?
- -Deployment: get a clear standards path for smart on fhir / cds-hooks (and alignment with UMA/Heart)
- -FM: work on alignment between FM resources and the rest of FHIR

Os dejamos la Agenda de los eventos de Aprendizaje
Health Level Seven® International | |||||||
|
Noticias relacionadas:
Computer World