Author: maestro

New Observation data model at the new subject SDMX

  By

SDMX is a standard for the codification of statistical information. Retrieving these types of data and inserting them in systems based on JSON/JSON-LD is a tough task performed by the project Interstat.

Thanks to its collaboration we have a new subject, dataModel.SDMX where these data models for mapping this standard will be located. this subject belongs to the Cross-Sector domain.

The first one is the Observation data model.

  • Observation. A single observation in the SDMX Cube, may have one or more associated measured values

Sdmx logo

New database of data models’ versions

  By , , , , , , , , , , , ,

In the main menu, it has been extended the submenu of list data models with a complete database of all versions of the data models.

It includes not only the data model, subject, and version but also the data directly linked to the raw version of the data model.

You can find it at Home -> List of data models -> List of data models versions.

Semantic-versioning

New data model Medication at subject HL7 (Health)

  By

In the new subject, Hl7 is being progressively mapped

The following data model is the Medication data model. In order to make it compatible with NGSI-LD some minor adjustments were necessary: 1) A limit in the recursive definition of data models has been applied (only 4 levels). 2) Change the ‘const’ clause in json schema by an enum of one value to make it compatible with YAML (open API 3.0). 3) the type attribute has been renamed to hl7type because otherwise conflicts with NGSI. Regarding the recursive definition of attributes, we expect that it would be more than enough for most of the practical applications. There are another 138 data models in the queue, and we hope they will be available soon. And other minor adjustments have been also included in the specification.

See it in subject Hl7 in the Smart Health domain.

  • Medication. This resource is primarily used for the identification and definition of a medication for the purposes of prescribing, dispensing, and administering medication as well as for making statements about medication use.

logo fhir

Release source code for some of the services. For python developers.

  By , , , , , , , , , , , ,

In the tools option of the main menu, there are a few services to help you to use, create and debug your data models.

Although working, some of these services are limited. We are releasing the code for some of the services to allow you to contribute with improvments.

It appears by the end of the page with texts like this:

“source code of this service if you want to improve it.”

Source code has an hyperlink pointing to the specific script in the utils directory.

They are created in python and connected to the WP forms in each option

Specifically

List of Adopters (use cases) and contributors available at Community menu

  By , , , , , , , , , , , ,

On the front page under the Community menu, there are two new entries
– Adopters: Lists the use cases documented in the different data models. It includes searchable facilities. It contains these fields:  adopter, description, mail, organization, project, comments, start date, subject and data model.

If you want to be listed, just make a PR on the file ADOPTERS.yaml of the data model folder. (The PR has to include an example ‘payload’ on how you use it)

– Contributors: Lists the people. It contains these fields:  name, surname, mail, organization, project, comments, year, and subject.

If you want to be listed you have to have contributed to any of the data models of the subject and then make a PR on the CONTRIBUTORS.yaml at the root of the subject.

In both cases the attributes are not mandatory so they can be empty.

New information customized for the different profiles

  By , , , , , , , , , , , ,

In the documentation menu (Home -> documentation -> Basic info for:), there are now 4 new options to provide you with the basic information depending on your profile

  • User. For those visitors with limited knowledge about what are the Smart Data Models
  • Contributor. For those visitors willing to extend or to contribute with new data models
  • Developer. For those visitors willing to integrate the data models with other tools or initiatives
  • Researcher. For those visitors whose aim is to understand what is agile standardization and how it is implemented at the Smart Data Models Program

If you have some of these profiles and you miss some information please let us know

Updating all specifications to make it easier to be updated

  By , , , , , , , , , , , ,

Initially, you will see few changes in the specifications of all data models,(it is in progress because it will last around 2 days to get it completed)

– The inclusion of the model for those attributes having it.

– Including the data type (when there is only one) for the attributes. ”

– A footer with some useful links, etc

Smart Data Models +++ Contribution Manual +++ About

but there is another hidden relevant change. The specifications are now divided into sections by these tags:

<!– section name –>

<!– /section name –>

It makes easier to update part of the specification without disrupting the rest of the content, and in most markdown viewers it is unnoticed. Besides this, it also allows the extension of the specification (if needed in a coming future) with new sections.

And, of course, everything can be done automatically. Thus we can keep being agile according to our principles.

Therefore, if you see that the specifications are presenting an update don’t worry, Initially, it is just the format and this new trick.

And welcome to the Chinese translation which is using this new format already.