#The model resource map how to#

You may also change the minimum and maximum cardinality of the element. For example, you could add an owner and add the resource type Person. You can either select a resource type (e.g. For each element, add a name and select one more data types that are supported by this element. A backbone is an element that has children elements, for example you could add an element named motor and add children elements for brand and type. Choose either an element or a backbone element. Now you can start adding elements in the Element Tree tab. In Forge, choose 'New Logical Model' (CTRL-M) and change the name, URL and file name in the properties tab. Let's say we want to create a model for Car.

#The model resource map how to#

How to build logical models in Forge?ДЇorge supports the creation of Logical Models.

After finishing the design process, your logical models can be used to share business requirements, but the actual FHIR implementation will depend on the corresponding profiles. Appointment, DiagnosticRequest, Procedure and so on). You will probably need to capture this information in more than one resource (e.g. For example, say you have modelled a clinical pathway. In other cases, the choices will be less clear. In some cases this will be easy, for example it will be natural to map a Patient model to the Patient resource. First, you will need to identify on which resources your logical models can be mapped. The next step will be to transform your logical models to one or more profiles. The logical model will usually also identify the required value sets. When using logical models early on in the design process your output will be one or more logical models describing the required data elements as well as their cardinality, data type and possible values. Note that these exchange standards have there own requirements and restrictions, which could result in information loss if you want to map DCMs to multiple standards for exchange. However, this still requires mappings from the DCM's to FHIR or for example CDA. This will make it easier for organizations to support multiple technical standards to exchange the same information. Their aim is to support the consistent use of medical data among different health care organizations and applications by ensuring that they all use the same common requirements. For instance, you could describe a blood pressure model and use this model to configure an EHR or to exchange data using CDA, HL7 V2, FHIR or any other standard. These building blocks are independent of the context in which they are used or the technical implementation. DCM's are basic information blocks that provide a way to structure medical information, combining expert knowledge, data specification and terminology. 2.2 Detailed clinical modelsДЄnother use of logical models is to describe Detailed Clinical Models (DCM's). Logical models can be very powerful in the interaction with the business or clinical community. Of course, the choice also depends on your domain experts and their affinity with FHIR. For these reasons, some may prefer to start building profiles directly. Be aware of the risk of creating very specific models that lead to potential rework and reconsideration of design choices. Time needs to be reserved in the design process to transform your logical models to actual profiles. There's a good possibility that your logical model will contain requirements that do not conform to the FHIR specification.

Note however that there will be a point in time where you will need to build profiles based on your logical models. Logical models bridge the gap between the business and the technical implementation.Logical models allow you to capture and document all requirements.There are no constraints in the structure of the model.

Logical models require minimal FHIR knowledge.

2.1 Logical models versus profilesДЄlthough it is not required to use logical models in the design process, there are some advantages compared to directly starting to build profiles: Logical models can be very useful during conversations with clinicians or other domain experts to gather requirements without being directly confined to the FHIR specification. Logical models can be used to communicate business requirements (data set, cardinality, terminology)in the early design process. The model could be used as input for building the final profiles and implementation guides. The logical model can be used to describe multiple resources or data objects or a single resource or data object. Each element in your data set should have a type specified, which can be either a resource, a data type or a custom type. The model describes your data set and consists of backbone elements with one or more (sub) elements. A logical model visualizes the domain in a tree model in the same way that a resource or profile is presented.