Prenatal monitoring in primary health care: a design science research-based approach to FHIR interoperability Authors: Renata D Braga, Plinio S Leitao-Junior, Suse B Castilho, Dandra A Souza, Lismary B Oliveira, Michael L D Oliveira, Luiselena L Esmeraldo, Carlos A G Tibiriçá, Diana F Guimarães, Aline R Nogueira, Livia M Vilela, Rejane F Ribeiro-Rotta, Fabio N Lucena, Juliana P Souza-Zinader Published: 2026 ABSTRACT AbstractBackgroundThis research addresses the development and validation of an information model for pregnancy monitoring that, through the Fast Healthcare Interoperability Resources (FHIR) specification, seeks to promote interoperability for the quality of prenatal care by multidisciplinary teams in Brazilian primary healthcare contexts. The Design Science Research (DSR) approach is applied to propose and evaluate the model, through quality strategies, where iterations increase the mode maturity in accordance with healthcare scenarios.ResultsA set of use cases is constructed from user stories in primary care that abstract health concepts for pregnancy monitoring. The information model is presented in a hierarchical structure, with the categorization of related concepts grouped into pillars, in the context of the integration of health professionals who work in a complementary manner. The traceability of the use cases in relation to the semantic pillars of the information model, the implementation of the model from a FHIR perspective, and how the model complies with the ISO 13972:2022 standard (Health informatics – Clinical information models - Characteristics, structures and requirements) are analyzed.ConclusionsThis work makes several key contributions, starting with the development of an information model for pregnancy monitoring. This model integrates different areas of primary care to promote a holistic and personalized approach to prenatal care. To ensure data can be shared effectively, it establishes health information interoperability using the HL7 FHIR R4 standard, which involved mapping resources and creating profiles as specified in an implementation guide. The study rigorously applies the Design Science Research method, utilizing multidisciplinary consensus strategies to scientifically improve and evolve the information model.Keywords: Health information interoperability, Prenatal care, FHIR, Fast health interoperability resources Background Digital transformation, the ongoing process of using digital technologies to transform businesses and services, is no longer a future possibility in healthcare but an urgent necessity [1]. An important goal is to promote the sharing and unequivocal interpretation of information to integrate systems, professionals, and organizations [2]. Semantic interoperability enables data sharing between organizations (e.g., healthcare units) and their internal ecosystem without loss of meaning [3]. The search for interoperability is one of the most pressing challenges for health systems and has required studies and research in recent years [4–6]. The lack of semantic interoperability potentially leads to inconsistent understanding of information among health professionals, which negatively impacts individual and community healthcare services [7, 8]. This negative effect is even more evident in extensive networks of health units, where the diversity of formats and recording methods can generate inconsistencies and failures in communication between the different points of care [9]. The search for a uniform representation of heterogeneous data has its specificity in each country, which is a consequence of its legislation and infrastructure [10]. In the case of Brazil, as a federative republic that encompasses 26 states, one federal district and more than 5,000 municipalities, there are hundreds of thousands of health care units, distributed across different regions, with geographic and population capillarity. Interoperability between information systems is urgent in this scenario, includes the availability of unambiguous understanding of information in all health domains, such as prenatal care. In the Brazilian constitution health is a right granted to each citizen. The Unified Health System (UHS) is the national public system for the provision of health care in all municipalities [11]. From a decentralized administrative point of view, the UHS is implemented by three entities [12]: Municipalities are responsible for the actual execution of basic care services. Municipalities are responsible for the actual execution of basic care services. States support specialized health services and more complex services. States support specialized health services and more complex services. The federal government moderates and defines national health policies, in addition to supporting financial resources. The federal government moderates and defines national health policies, in addition to supporting financial resources. In practice, these entities have coordinated actions: when one of the entities presents deficiencies in the execution of its competences, the others carry them out. Given the global demand for health information structural and semantic interoperability, which includes complexities of the Brazilian health system described above, the development of health information models (e.g. the structure and content of health concepts), combined with the adoption of international standards (e.g. HL7 FHIR - Fast Healthcare Interoperability Resources), has emerged as relevant initiatives for semantic interoperability, promoting the exchange of clinical data between systems and unambiguous interpretation of health information [13–18]. This research stems from a collaboration between the Goiás State Health Department (SES-GO) and the Federal University of Goiás (UFG), Brazil, focused on health interoperability and continuing education. A key objective is developing standardized information architectures, including health information models designed for consensus-based clinical scenarios. Within this context, prenatal care monitoring is a priority for the UHS, as highlighted by recent research [19–21]. This priority requires the development and implementation of interoperability-focused information models. According to the World Health Organization (WHO), prenatal care encompasses skilled health professionals’ provision of care to pregnant individuals, aiming to optimize health outcomes for both mother and fetus(es). Key components include risk identification, prevention, and management of pregnancy-related or comorbid conditions, health education, and health promotion [22]. This study aimed to develop and validate a standardized HL7 FHIR-based clinical information model for pregnancy monitoring in primary healthcare set tings of SES-GO, Brazil. The model was designed to promote semantic interoperability and integrated multidisciplinary care by harmonizing fragmented data from electronic health records, immunization registries, and laboratory systems. This integration enables longitudinal pregnancy health profiles accessible across care settings. Critically, the design process engaged nurses, physicians, health informaticians, and policymakers to ensure clinical relevance and alignment with real-world workflows, instead of idealized or theoretical ones [23]. Although the literature addresses health information models, such as in [13–18], to the best of our knowledge, this is the first scientific communication that explores pregnancy monitoring and its mapping to the FHIR standard in a context of multidisciplinary primary health care. Methods The study applies the Design Science Research (DSR) approach, which is based on the development and validation of artifacts relevant to solving real-world problems [24]. DSR seeks the production of knowledge in the form of design principles, models, research approaches and impacts of the use of technology [25]. DSR has been used in several fields of health [26–28]. Fig. 1 shows a DSR process, which is composed of activities, each with a defined artifact [29]. A Design Science Research (DSR) process cycle Awareness of problem activity Problem classification: Lack of interoperability between Health Information Systems, especially the absence of consistent structures to represent health information related to prenatal care. Problem impact: Variations in the structure and content of health information make health concepts unclear, ultimately reducing the quality of health services. Objectives/goals: (i) Identify use cases in the pregnancy monitoring domain, aiming to achieve awareness of the health concepts involved; (ii) Have a structured and standardized representation of these concepts, according to their usage scenarios. Existing solution for the problem class: Information Models use standards and terminologies to organize crucial health data, making it easier to record accurately and understand clearly. Solution specificity: The problem stems from the lack of FHIR-implemented information model for pregnancy monitoring. Such a model should consolidate essential data to support primary care, particularly for healthcare providers unfamiliar with the pregnant woman’s and fetus’s medical history. Suggestion activity Selecting a panel of experts An Expert Panel, comprising professionals from both institutions (SES-GO and UFG), was created with a multidisciplinary perspective and diversity of expertise, that is summarized in Table 1. Eligibility criteria for selection include: clinical experience in primary care; clinical experience in primary care; proficiency in health informatics and interoperability standards (e.g., HL7 FHIR); proficiency in health informatics and interoperability standards (e.g., HL7 FHIR); expertise in digital health, spanning education, research, policy, or innovation. expertise in digital health, spanning education, research, policy, or innovation. Table 1Expert panel: the diverse group of experts who participated in the researchCategoryOccupationProfileHealthGeneral physician Primary care physician Family doctor Nurse Nursing technician Dentist PharmacistAuditing in health systems specialist Clinical pharmacology specialist Digital health professor ICU nursing specialist Obstetrics specialist Oral/maxillofacial diseases specialist Primary care specialist Public health policy specialistICTComputer scientist ICT analyst Software engineerDigital health specialist FHIR specialist/researcher Health systems specialist ICT governance specialist Machine learning specialist Project management specialistBusinessAccountant Business analystBusiness intelligence specialist Public health policy specialist Expert panel: the diverse group of experts who participated in the research Development of preliminary health information model The Expert Panel is guided on problem, impact, objectives, solution specificity, and the artifact that represents the problem’s solution space. Through discussions (brainstorming) in regular collective and individual meetings, health concepts relevant to pregnancy monitoring are understood, and those that will preliminarily compose the information model are identified, where convergence is sought for: reducing the minimum and essential information, and their connections; reducing the minimum and essential information, and their connections; grouping the data elements into sets called pillars. grouping the data elements into sets called pillars. Finally, a preliminary mind map is constructed with the identified data elements, their connections, and pillars. Development and evaluation activities Development and evaluation activities follow an iterative and incremental approach, with each cycle encompassing: Goal Definition: Establish clear, specific objectives, such as incorporating new data or revising the model’s structure. Goal Definition: Establish clear, specific objectives, such as incorporating new data or revising the model’s structure. Incremental Execution: Modify the model in accordance with defined goals, recording all changes. Incremental Execution: Modify the model in accordance with defined goals, recording all changes. Incremental Validation: Evaluate the modified model through the Expert Panel, employing consensus-based strategies. Incremental Validation: Evaluate the modified model through the Expert Panel, employing consensus-based strategies. Documentation: Implement successfully validated modifications, signifying a model version increment and a maturation milestone. Documentation: Implement successfully validated modifications, signifying a model version increment and a maturation milestone. At each iteration, the expert panel evaluated the model to ensure it addressed the needs and perspectives in primary healthcare. Key assessment strategies included: Use case analysis: The model was tested in real clinical settings to confirm it accurately shows pregnancy monitoring data. Use case analysis: The model was tested in real clinical settings to confirm it accurately shows pregnancy monitoring data. Consensus meetings: Regular sessions were conducted to review test and simulation outcomes and identify model improvements. Consensus meetings: Regular sessions were conducted to review test and simulation outcomes and identify model improvements. The criteria for approving a maturity milestone are: Participation thresholds:Goal Definition: At least 50% of the group must participate.Incremental Execution: At least 50% of the group must participate.Incremental Validation: At least 50% + 1 of the group must participate. Participation thresholds:Goal Definition: At least 50% of the group must participate.Incremental Execution: At least 50% of the group must participate.Incremental Validation: At least 50% + 1 of the group must participate. Goal Definition: At least 50% of the group must participate. Goal Definition: At least 50% of the group must participate. Incremental Execution: At least 50% of the group must participate. Incremental Execution: At least 50% of the group must participate. Incremental Validation: At least 50% + 1 of the group must participate. Incremental Validation: At least 50% + 1 of the group must participate. Consensus rule (validation):Approval requires agreement from at least 50% + 1 of those who participated in the validation activity. Consensus rule (validation):Approval requires agreement from at least 50% + 1 of those who participated in the validation activity. Approval requires agreement from at least 50% + 1 of those who participated in the validation activity. Approval requires agreement from at least 50% + 1 of those who participated in the validation activity. Conclusion activity Research findings are consolidated, and scientific and practical contributions are communicated to ensure the generated knowledge is disseminated [25], as follows: Findings: Consolidation of the methodological and technical contributions. Findings: Consolidation of the methodological and technical contributions. Mapping information model to international standards: Alignment of the model with HL7 FHIR R4 and coding systems. Mapping information model to international standards: Alignment of the model with HL7 FHIR R4 and coding systems. Scientific papers: Artifact and the process instantiation are communicated. Scientific papers: Artifact and the process instantiation are communicated. Critical reflection: Model’s limitations for future iterations and applications. Critical reflection: Model’s limitations for future iterations and applications. Results According to the International Organization for Standardization (ISO), developing Clinical Information Models typically involves mentally mapping the domain to be modeled or preparing a use case specification [30]. In line with the methodology, we have applied both approaches: use case specification and domain mental mapping. Topics from use cases The expert panel generated the content of Fig. 2 as a data source for the domain under study (pregnancy monitoring). The figure represents the highlighted topics (subjects) of the use cases, that is, an abstraction derived from and representative of use cases. The intention was to map the health actors participating in each of the 17 identified topics and, importantly, to exemplify the relevant informational interests (i.e., the inherent health concepts) of the topic in question. The list of informational interests per topic can be extensive, but those exemplified in the figure seek to translate the understanding of the health concepts linked to each topic. The objective was to exemplify a list of health concepts representative of each topic, rather than being exhaustive or complete. A set of use case topics for pregnancy monitoring, as well as their informational interests Regarding a representation of the domain, user stories, used to capture patient and professional needs, guided use case development and reinforced user-centered design [31–33]. For example, in Intervention Timeline use case topic in Fig. 2: “As a nurse, I want to access a timeline with all clinical interventions and recorded guidelines, in order to check the progress of the follow-up”. The content of Fig. 2 is not intended to prioritize or sequence the use cases, but rather to present their representativeness in pregnancy monitoring, identifying the actors, needs, and relevant information for diverse primary healthcare scenarios in the Brazilian context. The actor set includes: Community health agent: Acts as a link between the community and health services, carrying out home visits and registering families. Community health agent: Acts as a link between the community and health services, carrying out home visits and registering families. Nurse: Responsible for low-risk prenatal consultations and for educational activities focused on selfcare and the prevention of complications. Nurse: Responsible for low-risk prenatal consultations and for educational activities focused on selfcare and the prevention of complications. Obstetric nurse: Enables the resolution of issues related to pregnancy and preparation for childbirth, serving as a link between primary care and birth assistance. Obstetric nurse: Enables the resolution of issues related to pregnancy and preparation for childbirth, serving as a link between primary care and birth assistance. General physician/Family doctor: Considers obstetric aspects and preexisting clinical conditions, and the family integration of the pregnant woman, with the ability to manage common comorbidities. General physician/Family doctor: Considers obstetric aspects and preexisting clinical conditions, and the family integration of the pregnant woman, with the ability to manage common comorbidities. Obstetrician: Acts as a support consultant or as a referral specialist, with deep knowledge of complex obstetric pathologies and their maternal-fetal repercussions. Obstetrician: Acts as a support consultant or as a referral specialist, with deep knowledge of complex obstetric pathologies and their maternal-fetal repercussions. Nutritionist: Provides support for the specific nutritional needs of each stage of pregnancy and associated clinical conditions. Nutritionist: Provides support for the specific nutritional needs of each stage of pregnancy and associated clinical conditions. Psychologist: Focuses on the emotional and psychosocial dimension of pregnancy, facilitating adaptation to motherhood and preventing mental disorders in the pregnancy-puerperal cycle. Psychologist: Focuses on the emotional and psychosocial dimension of pregnancy, facilitating adaptation to motherhood and preventing mental disorders in the pregnancy-puerperal cycle. Dentist: Provides specialized oral healthcare considering the physiological changes of pregnancy and prevention of systemic repercussions of oral diseases on pregnancy. Dentist: Provides specialized oral healthcare considering the physiological changes of pregnancy and prevention of systemic repercussions of oral diseases on pregnancy. The health concepts in Fig. 2 show the important health information for integrating primary care teams, as described in section “Methods”. For instance, in Obstetric History use case subject, the obstetrician seeks to access information about previous pregnancies and deliveries, so health concepts relevant are number of births, abortions, cesarean sections, high-risk pregnancies, and complications. Information model The information model addresses key healthcare concepts for primary care teams. We define a ‘health concept’ as a data point in the model, like BMI, or a medication dose. So we use data element and health concept interchangeably throughout the text. Figure 3 shows a mind map of the model’s data structure. It focuses only on the necessary key elements, considering the set of use cases, so some details (like patient details, dates, times, locations, and organizations) are omitted. The complete list of data elements can be found in the Implementation Guide [23]. Mind map illustrating the information model specifically designed for pregnancy monitoring The map indicates the model supports the monitoring from one to multiple pregnancies of a patient (Node “1..N Pregnancy”), making it possible to have a comprehensive view of gestational development over time. As foreseen in the methodology, data elements were categorized into “pillars”, so that each pillar brings together those concepts related in structure and/or purpose, namely clinical encounter, anthropometry, exam, medicinal product, and status. A pillar represents a core area of prenatal care. It is composed of a set of related health concepts that collectively form a specific perspective. For example, one pillar might be dedicated to the clinical encounter, which includes all information documenting the interaction between the patient and the healthcare professional. Clinical Encounter pillar summarizes encounters between patients and health professionals for assessment, intervention, and documentation of essential data: care unit, care professional, care specialty, care type, modality of service provision, risk classification, justification for the encounter, and care outcome. It records the longitudinal monitoring among different professionals, e.g., physicians, nurses, psychologists, nutritionists, and dentists. Anthropometric pillar refers to measuring, recording, and analyzing essential body measurements: height, weight, and body mass index (BMI). These provide objective indicators of the nutritional status and physical development of the pregnant woman and fetus. Exam pillar allows the communication and evaluation of the results of multidisciplinary exams. Basically, fundamental data elements are recorded, such as the requested test, which precisely identifies the type of clinical investigation required, and the result obtained, which documents the findings in a standardized manner. We use the term “medicinal product” to represent any substance (or combination of substances) that can be administered to patients for the treatment or prevention of diseases, with the intention of making a medical diagnosis, or to restore, correct, or modify physiological functions. In this sense, a medicinal product may contain one or more manufactured items and one or more pharmaceutical products. In Medicinal Product pillar, immunobiologicals are documented, which precisely identifies the vaccine agent or biological product administered, and the dose, recording the exact quantity of the medication prescribed and administered. This enables safe monitoring of the therapy instituted, allowing the traceability of the patient’s medication history and immunizations. The final pillar (Status) encapsulates the overall state of the pregnancy. It consolidates key data points, including temporal markers (e.g., last menstrual period, expected delivery date), outcome details, and a synthesis of clinical problems identified in other pillars. This comprehensive overview is crucial for identifying risk factors and tailoring the care plan to the specific needs of the patient and fetus. By gathering the most important health data for primary care during pregnancy, this model promotes consistent and complete recording of concepts according to use cases. The model also recognizes the integration of care episodes and the biopsychosocial complexity of pregnancy, as well as the need for a coordinated approach by professionals from different areas. Health concepts represented by coding systems in FHIR aim to have unambiguous interpretations of these concepts. The information model for prenatal monitoring is bound to international code systems and value sets, ensuring semantic interoperability through standardized public coding systems. Some examples are: ICD1 is used for the diagnostic categorization of associated conditions (Clinical Encounter pillar); LOINC2 2 is used for measurement elements, such as height, weight, and BMI, as well as requested laboratory examinations (Anthropometry and Exam pillars); and ICD and ICPC3 are applied to the pregnancy outcome (Status pillar). Discussion Use case traceability Regarding the information model consistency (stakeholders’ needs and requirements should be met), traceability allows the identification, relationship, and validation of the model’s data elements in relation to the information requirements. In other words, it seeks to map use cases in relation to model elements, checking whether the model covers the data needed for the use cases. Therefore, one question represents traceability in our investigation: which pillars of the information model encompass the health concepts of each use case? Consider Table 2, which presents a traceability matrix that relates each use case to the pillars that represent the health concepts in the information model. The first column represents the use case, and the remaining columns represent each of the pillars. If a table cell is marked with ‘\checkmark’, the pillar health concepts are among the concepts relevant to the use case. Table 2Use case traceability matrix in the information modelUse Case SubjectClinical EncounterAnthropometryExamMedicinal ProductStatusLaboratory test history\checkmarkMultidisciplinary records\checkmark\checkmark\checkmark\checkmark\checkmarkInstant clinical summary\checkmarkMedication adherence\checkmarkIntervention timeline\checkmark\checkmark\checkmarkVaccination status\checkmarkPending exams\checkmarkWarning signs guidance\checkmark\checkmarkRisk factors\checkmark\checkmarkClinical intercurrences\checkmarkObstetric history\checkmark\checkmark\checkmark\checkmark\checkmarkAppointments\checkmarkReproductive planning\checkmarkFetal development\checkmark\checkmarkDental health\checkmark\checkmark\checkmark\checkmarkMental health\checkmark\checkmark\checkmark\checkmarkNutritional guidance\checkmark\checkmark Use case traceability matrix in the information model For example, regarding Dental Health use case, the pertinent pillars are: Clinical Encounter because it records dental appointments; Exam because it records dental exams; Medicinal Product because it records medications prescribed during dental treatment; and Status because it records conditions and problems related to oral health. The traceability matrix highlights the interconnectedness between use cases in the context of pregnancy monitoring, analyzing the essential concepts for each scenario. This interdependence reinforces the need for a multidisciplinary and coordinated approach by healthcare professionals. A FHIR perspective for the information model Fast Healthcare Interoperability Resources (FHIR®) is an international standard developed by the Health Level Seven International (HL7®) to promote the electronic exchange of health information in a standardized manner [34]. In the Brazilian context, the National Health Data Network (NHDN) has adopted FHIR as a basis to ensure the standardization of the exchange of clinical and administrative data [35]. FHIR resources The core of FHIR is having a resource-oriented model, with each resource representing a healthcare entity such as a patient, a medication, or a clinical condition. In other words, each resource in FHIR is a modular, reusable unit designed to represent essential clinical or administrative data. There are over 150 resources defined in FHIR, seeking to be complete in covering health concepts [35]. Therefore, the understanding of FHIR resources is essential for professionals involved in interoperability and integration projects of health systems. Correct mapping of health concepts and events from the clinical information domain to FHIR resources ensures that the semantics and integrity of data are maintained throughout the electronic transmission of information. FHIR resource mapping The expert panel worked together to enable collaborative interaction between clinical concept experts (healthcare professionals) and interoperability experts (information technology and digital health professionals): healthcare professionals provided detailed and validated expertise on the definition and application of key clinical concepts, while FHIR experts used this expertise to accurately map these concepts to FHIR resources. Figure 4 extends Fig. 3 by adding the mapping of the information model to FHIR resources and pertinent data elements, highlighted in red font. The descriptions below introduce resources and their data elements in parentheses: For a pregnant woman (Patient), there is a monitoring of her pregnancies. Each pregnancy (EpisodeOfCare) is described by clinical encounters (Encounter), anthropometric measurements (Observation), exams (ServiceRequest, DiagnosticReport), medicinal products (Immunization) and a state (Observation, Condition). For a pregnant woman (Patient), there is a monitoring of her pregnancies. Each pregnancy (EpisodeOfCare) is described by clinical encounters (Encounter), anthropometric measurements (Observation), exams (ServiceRequest, DiagnosticReport), medicinal products (Immunization) and a state (Observation, Condition). A clinical encounter is described by a healthcare unit (Encounter.serviceProvider, i.e. a reference to Organization), a healthcare professional (Encounter.participant.individual.practitioner, i.e. a reference to Practitioner), a healthcare specialty (Encounter.participant.individual, i.e. a reference to PractitionerRole), a type of care (Encounter.type), a modality of service provision (Encounter.class), a risk classification (Encounter.priority), and even several justifications for the clinical encounter. Each justification in turn has a cause (Encounter.reasonReference, i.e. a reference to Condition), up to several outcomes (Encounter.hospitalization.dischargeDisposition), and up to several referrals (ServiceRequest). A clinical encounter is described by a healthcare unit (Encounter.serviceProvider, i.e. a reference to Organization), a healthcare professional (Encounter.participant.individual.practitioner, i.e. a reference to Practitioner), a healthcare specialty (Encounter.participant.individual, i.e. a reference to PractitionerRole), a type of care (Encounter.type), a modality of service provision (Encounter.class), a risk classification (Encounter.priority), and even several justifications for the clinical encounter. Each justification in turn has a cause (Encounter.reasonReference, i.e. a reference to Condition), up to several outcomes (Encounter.hospitalization.dischargeDisposition), and up to several referrals (ServiceRequest). Similar descriptions apply to Anthropometric, Exam, Medicinal Product, and Status pillars. Similar descriptions apply to Anthropometric, Exam, Medicinal Product, and Status pillars. Mapping the information model to FHIR resources (red text denotes FHIR resources mapping model elements) In summary a detailed analysis of the information model’s elements was conducted, aiming at understanding the contexts of use and the selection, customization or extension of FHIR resources aiming at preserving semantics, granularity and data integrity. The complete mapping is documented in the Implementation Guide [23]. FHIR implementation guide A FHIR Implementation Guide (IG) is a technical document that guides developers, analysts, and healthcare professionals in the consistent, interoperable, and secure adoption of FHIR resources in real-world digital health contexts. The full implementation guide for pregnancy monitoring is available [23]. On developing the IG, FHIR resources and attributes were used to define the technical structure of each concept, promoting semantic and syntactic interoperability. Each data element is linked to a value domain, often expressed through standardized terminologies (e.g., LOINC, SNOMED-CT, ICD-11), and implemented using HL7 FHIR Release 4 (R4) structures. FHIR profiling was conducted using tools such as SUSHI4 and SIMPLIFIER5, ensuring alignment with HL7 FHIR R4 and Brazilian terminology artifacts (e.g., imunizacao-gestante6). Adequacy of the information model according to ISO 13972:2022 standard ISO 13972:2022 standard (Health informatics – Clinical information models - Characteristics, structures and requirements) describes requirements for content, structure and context of clinical information models and the specification of their data elements, data element relationships, metadata and version control. Compliance with the requirements of the standard promotes the interoperability of healthcare information, in addition to having clinical data represented in a more consistent and structured manner [30]. Regarding the analysis of how the information model and its process adhere to the main key requirements addressed in the standard, it was mainly based on Section 6 of the standard, namely: Clinical Information Model Content, Structure and Requirements [30]. The analysis categorizes (groups) the requirements and principles as follows. General and scope requirements Purpose: Summary of records relating to health entities that occurred mainly during pregnancy. Purpose: Summary of records relating to health entities that occurred mainly during pregnancy. Scope: Essential concepts for healthcare by a multidisciplinary team in the context of primary care. Scope: Essential concepts for healthcare by a multidisciplinary team in the context of primary care. Population: Pregnant woman, fetus(es), primary care health professionals. Population: Pregnant woman, fetus(es), primary care health professionals. Focus/justification: Pregnancy monitoring, in having unambiguous interpretation of health information, by those who use them in the operation and management of health services, including health professionals not familiar with the health history of the pregnant woman and fetus. Focus/justification: Pregnancy monitoring, in having unambiguous interpretation of health information, by those who use them in the operation and management of health services, including health professionals not familiar with the health history of the pregnant woman and fetus. Structural and content requirements Internal structure: Hierarchy of data elements (health concepts), grouped into pillars for related concepts in healthcare. Internal structure: Hierarchy of data elements (health concepts), grouped into pillars for related concepts in healthcare. Concept description: Unambiguous description of each element from their attributes: name, semantic definition, data type, cardinality, optionality, allowed values (element domain, includes terminology), and restrictions, all addressed in the implementation guide [23]. Concept description: Unambiguous description of each element from their attributes: name, semantic definition, data type, cardinality, optionality, allowed values (element domain, includes terminology), and restrictions, all addressed in the implementation guide [23]. Profile definition (profiling): Defining resource adaptations to context, scenarios and use cases through profiles (e.g. Requested Exam profile 7). Profile definition (profiling): Defining resource adaptations to context, scenarios and use cases through profiles (e.g. Requested Exam profile 7). Semantic and terminology requirements Granularity: Hierarchy of data elements and semantic pillars as structural granularity; record of one to multiple pregnancies of a patient as temporal and event granularity. Granularity: Hierarchy of data elements and semantic pillars as structural granularity; record of one to multiple pregnancies of a patient as temporal and event granularity. Standards compliance: FHIR as the standard for content and information exchange; coding systems addressed in the Implementation Guide (e.g. LOINC for exams). Standards compliance: FHIR as the standard for content and information exchange; coding systems addressed in the Implementation Guide (e.g. LOINC for exams). Consistency and validation requirements Use case orientation: Model development based on clinical use cases, with multidisciplinary perspectives for healthcare and validation by consensus strategies. Use case orientation: Model development based on clinical use cases, with multidisciplinary perspectives for healthcare and validation by consensus strategies. Validation process: Model maturation increments validated by the expert panel in consensus strategies and adherence to use cases. Validation process: Model maturation increments validated by the expert panel in consensus strategies and adherence to use cases. Model traceability: Specification of the core health concepts involved in each use case, that enables the tracing of such concepts back to the semantic pillars and consequently to the data elements of the model. Model traceability: Specification of the core health concepts involved in each use case, that enables the tracing of such concepts back to the semantic pillars and consequently to the data elements of the model. Versioning and maintenance requirements Versioning: Evolution control of the information model is moving to the GitHub tool, in order to track changes over time and promote compatibility or migration between versions (under implementation). Versioning: Evolution control of the information model is moving to the GitHub tool, in order to track changes over time and promote compatibility or migration between versions (under implementation). Governance: Maintenance and publication of the model has a governance structure and policy definition (under approval). Governance: Maintenance and publication of the model has a governance structure and policy definition (under approval). Regarding the development process of information models, the standard states “approaches often used include mind mapping of the domain that needs to be modeled or the preparation of a use case specification for one or more purposes” [30]. We have applied both approaches: use case specification and domain mind mapping, developed collaboratively and refined iteratively through shared editing sessions, to structure and relate key data elements. This dual-method approach supports a shared understanding between clinical and technical stakeholders. Conclusion This paper refers to a scientific communication planned within the framework of research cooperation between the academic community and healthcare professionals in the context of primary public health care. The research explores the process and artifacts involved in developing an information model for pregnancy monitoring, from its conception to its implementation: Definition of use cases → Abstraction of health concepts → Development of the information model and its presentation in the form of a mind map, with its data elements grouped into information pillars → Selection of appropriate FHIR resources for the elements of the information model → Definition of profiles according to the selected FHIR resources, the specification of which is in an implementation guide [23]. Definition of use cases → Abstraction of health concepts → Development of the information model and its presentation in the form of a mind map, with its data elements grouped into information pillars → Selection of appropriate FHIR resources for the elements of the information model → Definition of profiles according to the selected FHIR resources, the specification of which is in an implementation guide [23]. Some of the contributions generated by the work are: Multidisciplinary healthcare based on use cases: The development of the information model for pregnancy monitoring integrates different areas of healthcare for primary care. Based on “use cases”, the model foresees collaboration between obstetricians, nurses, nutritionists and other professionals, ensuring a holistic and personalized approach to prenatal care. Multidisciplinary healthcare based on use cases: The development of the information model for pregnancy monitoring integrates different areas of healthcare for primary care. Based on “use cases”, the model foresees collaboration between obstetricians, nurses, nutritionists and other professionals, ensuring a holistic and personalized approach to prenatal care. Interoperability with HL7 FHIR R4 standard and encoding systems: The information model for pregnancy monitoring, once compliant with the HL7 FHIR R4 standard, promotes interoperability between health systems for the efficient exchange of clinical data. It covers demographic and clinical information, as well as obstetric history and risk assessments, using coding systems such as ICD for clinical encounter reasons and LOINC for laboratory tests. Interoperability with HL7 FHIR R4 standard and encoding systems: The information model for pregnancy monitoring, once compliant with the HL7 FHIR R4 standard, promotes interoperability between health systems for the efficient exchange of clinical data. It covers demographic and clinical information, as well as obstetric history and risk assessments, using coding systems such as ICD for clinical encounter reasons and LOINC for laboratory tests. Instantiation of the Design Science Research (DSR) method: Applying the method as a research focus adds knowledge by employing a systematic approach to the definition, construction, and validation of artifacts. Because science requires validation through rigorous methods, artifacts are continually evaluated from both theoretical and practical perspectives: the former, enriching the scientific literature with new models and methodologies; the latter, developing new technologies. Furthermore, DSR applied to pregnancy monitoring potentially adds value by integrating multidisciplinary knowledge, such as that of primary healthcare. Instantiation of the Design Science Research (DSR) method: Applying the method as a research focus adds knowledge by employing a systematic approach to the definition, construction, and validation of artifacts. Because science requires validation through rigorous methods, artifacts are continually evaluated from both theoretical and practical perspectives: the former, enriching the scientific literature with new models and methodologies; the latter, developing new technologies. Furthermore, DSR applied to pregnancy monitoring potentially adds value by integrating multidisciplinary knowledge, such as that of primary healthcare. With respect to resolving threats to validity: Internal validity: Selection criteria were applied to the expert panel composition, considering the diversity of expertise, integrating clinical, technical and management knowledge. This process prevents any single professional perspective from disproportionately influencing the outcomes. Internal validity: Selection criteria were applied to the expert panel composition, considering the diversity of expertise, integrating clinical, technical and management knowledge. This process prevents any single professional perspective from disproportionately influencing the outcomes. External validity: Consensus strategies and requirements promote the validation and generalization of the model in the context of the domain (pregnancy monitoring). By grounding the model in a diverse and collective agreement, its potential for successful transferability and adoption is significantly enhanced. External validity: Consensus strategies and requirements promote the validation and generalization of the model in the context of the domain (pregnancy monitoring). By grounding the model in a diverse and collective agreement, its potential for successful transferability and adoption is significantly enhanced. Construct validity: Health concepts were defined according to the knowledge and experience of the expert panel, which promotes the findings as evidence of the consistency and interoperability of health information. The definitions are explicitly documented in the implementation guide, providing a transparent and solid foundation for the model. Construct validity: Health concepts were defined according to the knowledge and experience of the expert panel, which promotes the findings as evidence of the consistency and interoperability of health information. The definitions are explicitly documented in the implementation guide, providing a transparent and solid foundation for the model. A pilot proof-of-concept study was conducted to evaluate the feasibility of the information model in collecting data for prenatal monitoring, by analyzing data from hundreds of pregnancies available in primary health care. The model successfully supported the intended use cases and preliminarily allowed for the coherent organization of prenatal information. Some future developments are planned: a comprehensive, large-scale, and quantitative evaluation to measure improvements in data completeness and the success of interoperability, although a proof-of-concept pilot experiment was conducted for the model; a comprehensive, large-scale, and quantitative evaluation to measure improvements in data completeness and the success of interoperability, although a proof-of-concept pilot experiment was conducted for the model; a consistent semantic grounding by aligning the information model with the ISO 13940:2015 standard (Health informatics – System of concepts to support continuity of care) [36], in order to formalize its conceptual foundation, i.e. to bridge the gap between the informational content and its pragmatic process context [37]; a consistent semantic grounding by aligning the information model with the ISO 13940:2015 standard (Health informatics – System of concepts to support continuity of care) [36], in order to formalize its conceptual foundation, i.e. to bridge the gap between the informational content and its pragmatic process context [37]; a comprehensive investigation in favor of global inclusion to promote an adaptable model for other low- and middle-income countries (LMICs), in order to overcome data fragmentation and improve continuity of care in prenatal services [38]. a comprehensive investigation in favor of global inclusion to promote an adaptable model for other low- and middle-income countries (LMICs), in order to overcome data fragmentation and improve continuity of care in prenatal services [38]. Acknowledgements In addition to paper authors, this work had the collaboration of 22 professionals from the Goiás State Health Department (SES-GO) and the Federal University of Goiás (UFG), namely: UFG - Daniel Nogueira da Costa, Flávio Guimarães de Abreu Azevedo, Murilo Lopes da Luz, and Mariana Soller Ramada. SES-GO - Adriano de Castro Freitas, Angela Barbosa, Arlon da Silva Moreira, Carolina de Paula Nunes Barbosa Quintão, Cassio Oliveira Camilo, Cristiane da Silva Mendonça Longo, Christyne Maroclo Gomes Jacob dos Santos, Daniel Batista Gomes, Diogo Antônio Leal, Esrom Vieira Cruz dos Santos, Evaristo Otávio Bueno, Fernando Cavalcante Miranda, Igor de Oliveira Jardim, Pedro Manuel Rodrigues Lima de Moura, Robson Carlos Silverio de Jesus, Tatiana Feitosa Araujo, Thiago dos Santos Prado, and Wanderson da Silva Marques. Author contributions Contributions according to CRediT (Contributor Role Taxonomy on https://credit.niso.org/): Aline R. Nogueira (Methodology, Validation), Carlos A. G. Tibiriçá (Conceptualization, Methodology, Validation), Dandra A. Souza (Methodology, Validation), Diana F. Guimarães (Project Administration, Validation), Fabio N. Lucena (Methodology, Validation, Writing – Review & Editing), Juliana P. Souza-Zinader (Conceptualization, Methodology, Project Administration, Validation, Writing – Review & Editing), Lismary B. Oliveira (Methodology, Validation), Livia M. Vilela (Methodology, Validation), Luiselena L. Esmeraldo (Project Administration), Michael L. D. Oliveira (Methodology, Validation), Plinio S. Leitao-Junior (Validation, Writing – Original Draft, Writing – Review & Editing), Rejane F. Ribeiro-Rotta (Validation), Renata D. Braga (Conceptualization, Methodology, Validation, Writing – Original Draft, Writing – Review & Editing), Suse B. Castilho (Methodology, Validation). Funding No Funding. Data availability A complete structure and semantics of the data are fully defined and publicly available at https://fhir.saude.go.gov.br/r4/saude-mulher/StructureDefinition/prenatal-gestante (provided by the Goiás State Health Department). This location provides all metadata, ValueSets, profiles, and so forth. The corresponding Implementation Guide includes sufficient examples of FHIR resources that illustrate the expected data format and can be used to understand and reproduce the data processing and interoperability mechanisms described in this work. Declarations Ethics approval and consent to participate Not applicable. Consent for publication Not applicable. Competing interests The authors declare no competing interests. Footnotes https://icd.who.int/en/ https://loinc.org/ https://wicc.one/icpc-classification https://www.hl7.org/fhir/uv/shorthand/2020May/sushi.html https://simplifier.net https://fhir.saude.go.gov.br/r4/saude-mulher/ValueSet/imunizacao-gestante https://fhir.saude.go.gov.br/r4/saude-mulher/StructureDefinition-exame-solicitado.html Publisher’s Note Springer Nature remains neutral with regard to jurisdictional claims in published maps and institutional affiliations. References Associated Data Data Availability Statement A complete structure and semantics of the data are fully defined and publicly available at https://fhir.saude.go.gov.br/r4/saude-mulher/StructureDefinition/prenatal-gestante (provided by the Goiás State Health Department). This location provides all metadata, ValueSets, profiles, and so forth. The corresponding Implementation Guide includes sufficient examples of FHIR resources that illustrate the expected data format and can be used to understand and reproduce the data processing and interoperability mechanisms described in this work.