Nova postagem

查找

Anúncio
· 2 hr atrás

Kick-off Webinar for InterSystems Full Stack Contest 2026

Hey Community,

We're pleased to invite everyone to the upcoming kick-off Webinar for the InterSystems Full Stack Contest!

During the webinar, you will discover the exciting challenges and opportunities that await developers in this contest. We will also discuss the topics we would like the participants to cover and show you how to develop, build, and deploy applications using the InterSystems IRIS data platform.

Date & Time: Monday, February 2 – 12:00 pm EST | 6:00 pm CET  

Speakers:  
🗣  @Derek Gervais, Developer Relations Evangelist
🗣 ​​​@Evgeny Shvarov, Senior Manager of Developer and Startup Programs
🗣 @Raj Singh, Product Manager - Developer Experience

✅ Register for the kick-off today!

Discussão (0)1
Entre ou crie uma conta para continuar
Artigo
· 4 hr atrás 8min de leitura

Why Choosing the Right Custom Healthcare Software Development Company Matters in 2026 and Beyond

Introduction

The healthcare industry is going through one of the most significant digital transformations in its history. From hospitals and clinics to diagnostic labs, pharmacies, insurance providers, and telemedicine startups, every healthcare organization today relies heavily on technology to deliver safe, efficient, and patient‑centric services. At the heart of this transformation lies one critical factor: choosing the right Custom Healthcare Software Development Company.

Healthcare is no longer just about treatment; it is about experience, accuracy, compliance, and scalability. Off‑the‑shelf software often fails to address the complex workflows, regulatory requirements, and data security needs of healthcare organizations. This is where a professional Custom Healthcare Software Development Company becomes essential. Custom‑built solutions are designed to align with real clinical processes, business goals, and long‑term digital strategies.

This in‑depth Technology and Business article explores how a Custom Healthcare Software Development Company supports modern healthcare organizations, why custom healthcare solutions are future‑proof, and how businesses can achieve long‑term ROI through tailored digital systems. The article is written in a natural, human style, fully optimized for search engines, and structured to remain relevant well into 2026 and beyond.


Understanding Custom Healthcare Software Development

Custom healthcare software development refers to the design, development, and deployment of software solutions that are specifically built for healthcare organizations based on their unique operational, clinical, and administrative needs. Unlike generic healthcare platforms, custom solutions adapt to the organization instead of forcing the organization to adapt to the software.

A reliable Custom Healthcare Software Development Company works closely with healthcare providers to understand their workflows, challenges, compliance requirements, and growth plans. The result is a system that improves efficiency, enhances patient care, and ensures regulatory compliance without unnecessary complexity.

Healthcare organizations often require software that integrates multiple departments, supports large volumes of sensitive patient data, and scales as services expand. Custom development ensures flexibility, interoperability, and long‑term sustainability.


Why Healthcare Organizations Are Moving Toward Custom Solutions

Complex Healthcare Workflows

Healthcare workflows are rarely linear. From patient registration and diagnosis to treatment, billing, and follow‑up care, every step involves multiple stakeholders and systems. A Custom Healthcare Software Development Company designs solutions that mirror these real‑world workflows, reducing errors and improving coordination.

Regulatory and Compliance Requirements

Healthcare software must comply with strict regulations such as HIPAA, HL7, GDPR, and regional healthcare laws. Custom solutions are built with compliance in mind from day one, ensuring data privacy, audit readiness, and secure information exchange.

Data Security and Privacy

Healthcare data is among the most sensitive types of information. Custom healthcare software allows organizations to implement advanced security protocols, access controls, and encryption standards tailored to their risk profile.

Scalability and Future Readiness

As healthcare organizations grow, their software must scale with them. A Custom Healthcare Software Development Company builds modular and flexible systems that support future expansion, new services, and emerging technologies.


Role of a Custom Healthcare Software Development Company

A professional Custom Healthcare Software Development Company does far more than just write code. It acts as a long‑term technology partner that supports healthcare organizations throughout their digital journey.

Key responsibilities include:

  • Business and technical requirement analysis
  • Healthcare workflow mapping
  • UI/UX design for clinical and non‑clinical users
  • Secure software architecture planning
  • Integration with existing systems
  • Regulatory compliance implementation
  • Testing, deployment, and maintenance

By combining technical expertise with healthcare domain knowledge, a trusted development partner ensures that the final solution delivers measurable value.


Types of Solutions Developed by a Custom Healthcare Software Development Company

Electronic Health Records (EHR) and EMR Systems

Custom EHR and EMR systems allow healthcare providers to manage patient records efficiently while ensuring accuracy and compliance. These systems can be tailored to specific specialties, departments, or care models.

Hospital Management Systems

Hospital management software integrates multiple operational areas such as patient administration, staff scheduling, billing, inventory, and reporting. Custom development ensures seamless coordination across departments.

Telemedicine and Remote Care Platforms

Telehealth solutions enable virtual consultations, remote monitoring, and digital follow‑ups. A Custom Healthcare Software Development Company builds secure and user‑friendly platforms that enhance patient accessibility.

Healthcare Mobile Applications

Custom mobile apps support appointment scheduling, prescription management, patient engagement, and remote health tracking. These apps improve communication between providers and patients.

Medical Billing and Revenue Cycle Management

Custom billing software reduces claim errors, accelerates reimbursements, and improves financial transparency. Tailored solutions adapt to local insurance policies and billing workflows.

Healthcare Analytics and Reporting Tools

Data‑driven decision‑making is essential in modern healthcare. Custom analytics platforms help organizations track performance, predict trends, and improve outcomes.


Business Benefits of Custom Healthcare Software Development

Improved Operational Efficiency

Custom software eliminates redundant tasks and automates manual processes, allowing healthcare staff to focus more on patient care.

Enhanced Patient Experience

User‑centric design improves patient engagement, communication, and satisfaction. Personalized digital experiences lead to better outcomes.

Cost Optimization

While custom development requires an initial investment, it reduces long‑term costs associated with licensing, inefficiencies, and system limitations.

Competitive Advantage

Healthcare organizations using tailored digital solutions are better positioned to innovate, adapt, and compete in a rapidly evolving market.

Long‑Term ROI

A Custom Healthcare Software Development Company builds systems that grow with the organization, delivering sustained value over time.


Importance of Custom Healthcare Software Development Services

When healthcare organizations invest in custom Healthcare software development services, they gain access to expertise that bridges technology and healthcare operations. These services ensure that every feature aligns with clinical goals and business objectives.

Professional custom Healthcare software development services cover the entire software lifecycle, from concept and design to deployment and continuous improvement. This holistic approach ensures stability, compliance, and adaptability.

Healthcare providers that rely on experienced development services benefit from faster digital transformation, reduced risks, and higher system adoption rates.


Integration Capabilities and Interoperability

Healthcare systems rarely operate in isolation. Custom solutions must integrate with existing platforms such as laboratory systems, pharmacy software, insurance databases, and third‑party medical devices.

A skilled Custom Healthcare Software Development Company ensures interoperability through standardized protocols and secure APIs. This enables seamless data exchange and coordinated care delivery.


Emerging Technologies Shaping Healthcare Software in 2026

Artificial Intelligence and Machine Learning

AI‑powered healthcare software supports diagnostics, predictive analytics, and personalized treatment plans.

Internet of Medical Things (IoMT)

Connected medical devices generate real‑time patient data, improving monitoring and preventive care.

Cloud‑Based Healthcare Systems

Cloud infrastructure enhances scalability, accessibility, and cost efficiency while maintaining security.

Blockchain for Healthcare Data Security

Blockchain technology improves data integrity, transparency, and trust in healthcare information systems.

A future‑focused Custom Healthcare Software Development Company designs solutions that are ready to adopt these technologies as they mature.


Choosing the Right Custom Healthcare Software Development Company

Selecting the right partner is critical for project success. Healthcare organizations should evaluate potential development companies based on:

  • Healthcare domain experience
  • Compliance and security expertise
  • Technical capabilities
  • Communication and collaboration approach
  • Long‑term support and scalability planning

A company like Digitrends, offering professional healthcare solutions through its dedicated Custom Healthcare Software Development Company expertise, understands both technical innovation and healthcare realities.


Future‑Proofing Healthcare Businesses Through Custom Software

Healthcare organizations that invest in custom solutions are better prepared for regulatory changes, technological advancements, and evolving patient expectations. A strong digital foundation enables continuous innovation without operational disruption.

By partnering with a trusted Custom Healthcare Software Development Company, healthcare businesses ensure that their technology strategy remains aligned with future demands.


Conclusion

The healthcare industry’s future depends on intelligent, secure, and scalable digital solutions. A professional Custom Healthcare Software Development Company plays a vital role in helping healthcare organizations deliver better care, improve efficiency, and achieve long‑term business success.

Through tailored systems, advanced security, and future‑ready architecture, custom healthcare software empowers organizations to meet today’s challenges and tomorrow’s opportunities. Investing in the right development partner is not just a technology decision; it is a strategic business move that defines the future of healthcare delivery.

Discussão (0)1
Entre ou crie uma conta para continuar
Artigo
· 4 hr atrás 5min de leitura

The Ultimate Guide To Tax Advice For Expats In 2026

 

Navigating taxes as an American expat can feel overwhelming, especially with 2026's updated IRS rules and global compliance demands. Whether you're filing a tax return in Switzerland or another country, this guide delivers practical tax advice for expats to minimise liabilities, stay compliant, and optimise your finances. From U.S. filing basics to smart planning strategies, we'll cover everything you need to thrive abroad.

1. Filing U.S. Taxes Abroad (for American Expats)

American residents and green card holders must file U.S. taxes on worldwide income, no matter where they live—this is the infamous "citizenship-based taxation" that sets the U.S. apart from most nations. In 2026, the IRS continues enforcing this through forms like the FBAR (for foreign accounts over $10,000) and FATCA (Form 8938 for assets exceeding thresholds).

Start with Form 1040. Even if you owe nothing due to exclusions, file by June 15 for expats (automatic extension from April 15). Key relief: The Foreign Earned Income Exclusion (FEIE) lets you exclude up to $130,000 (adjusted for 2026 inflation) of foreign-earned income if you meet the Physical Presence Test (330 days abroad) or Bona Fide Residence Test. Pair it with the Foreign Tax Credit (FTC) to offset U.S. taxes with credits for foreign taxes paid—crucial for dual filers in high-tax spots like Switzerland.

For "tax return Switzerland" filers, report Swiss bank accounts via FBAR by April 15 (auto-extension to October). Miss it? Penalties start at $10,000 per account. Use IRS Free File or expat software like TaxAct for simplicity. Pro tip: If self-employed, tackle Schedule C and self-employment taxes (15.3%), but deduct business expenses aggressively.

Real-world example: A Zurich-based consultant earning $150,000 excludes $130,000 via FEIE, credits Swiss taxes on the rest, and owes zero U.S. tax. Always consult a pro—errors lead to audits.

2. Expat Tax Planning Strategies for 2026

2026 brings tweaks like higher standard deductions ($15,000 single/$30,000 married) and expanded Roth IRA contributions for expats. Smart tax advice for expats starts with preemptive planning.

  • Maximise Exclusions and Credits: Combine FEIE with FTC—don't double-dip, as IRS rules prohibit it. Housing exclusions add up to $40,000+ in pricey locales.
  • Retirement Accounts: Contribute to a Solo 401(k) (up to $70,000) or SEP-IRA for tax-deferred growth. Expats can use offshore brokers compliant with IRS rules.
  • HSAs and FSAs: If eligible via a U.S. employer, these offer triple tax benefits—deduct contributions, grow tax-free, and withdraw tax-free for medical.
  • Quarterly Estimated Payments: Pay U.S. estimates via Form 1040-ES to avoid underpayment penalties (110% of prior year's tax).

For Switzerland expats, leverage the U.S.-Switzerland tax treaty to avoid double taxation on pensions and dividends. Time asset sales for capital gains rates (0-20%), and use opportunity zones if repatriating funds. Advanced move: Elect Foreign Housing Deduction for rent exceeding 16% of salary.

Track everything with apps like Expensify. Annual planning saves thousands—schedule a consult with specialists like 1291 Group for personalized 2026 strategies.

3. Choosing a Tax-Friendly Country

Not all destinations are equal for tax advice for expats. Prioritise treaty countries to sidestep double taxation. Top picks for 2026:

Country

Key Benefits

U.S. Treaty Perks

Avg. Tax Rate

Expat Drawbacks

Switzerland

Low cantonal taxes (Zug: 12-15%), no wealth tax in some areas

Dividends/pensions protected

20-40% combined

High living costs, complex "tax return Switzerland" filing

Portugal

NHR program: 10% flat on pensions (phasing out 2026)

Full treaty coverage

10-20% effective

EU bureaucracy

Malaysia

MM2H visa, no tax on foreign income

Partial treaty

0-28% local

Tropical climate not for all

UAE

Zero income tax

No treaty, but FEIE covers

0%

Hot summers, no citizenship path

Costa Rica

Territorial tax (foreign income untaxed)

Treaty in works

0-25%

Infrastructure varies

Switzerland shines for professionals—its treaty credits U.S. taxes against Swiss liabilities, ideal for high earners. Avoid non-treaty nations like Thailand to prevent 30% withholding on U.S. dividends. Factor in residency tests, cost of living, and family needs. Use tools like PwC's Worldwide Tax Summaries for comparisons.

4. Avoiding Excess Tax Liability (Legally)

   

No one wants an IRS love letter. Legal tax advice for expats focuses on compliance over evasion—penalties hit 75% for fraud.

  • Report Everything: Disclose foreign trusts (Form 3520), corporations (5471), and partnerships (8865). Streamline non-willful non-compliance via OVDP successors.
  • Treaty Shopping: Live in treaty countries; claim benefits on Form 8833.
  • Exit Strategies: Renounce citizenship? File final taxes plus exit tax on unrealized gains over $2M net worth (FBAR required post-renunciation).
  • Audit-Proofing: Keep 7-year records. Use PFICs carefully—elect QEF to avoid punitive taxes.

Switzerland-specific: File cantonal returns by March 31; U.S. data-sharing via FATCA means hiding is futile. Common pitfall: Forgetting Social Security Totalization Agreement—avoids dual contributions.

Hire enrolled agents or CPAs with EA credentials for bulletproof filings.

5. Key Principles for Tax Efficiency

Build lasting wealth with these timeless principles, updated for 2026:

  1. Diversify Income: Mix salary (FEIE-eligible), investments (treaty-protected), and rentals (depreciation deductions).
  2. Defer and Convert: Roth conversions in low-income years; delay Social Security until 70 for 8% annual boosts.
  3. Entity Structures: Form LLCs or S-Corps for U.S. business; offshore companies only if IRS-approved.
  4. Family Planning: Gift $18,000/person annually tax-free; education savings via 529s.
  5. Tech Leverage: Automate with TurboTax Deluxe or Greenback Expat Tax Services.

Efficiency = compliance + optimization. Aim for effective rates under 15% through smart moves.

6. Additional Guidance

  • Deadlines: U.S. auto-extension to June 15; Switzerland varies by canton (Zurich: March 31).
  • Resources: IRS Publication 54, State Department expat guides, Treaty texts on Treasury.gov.
  • Professional Help: DIY risks fines—partner with firms like 1291 Group for "tax return Switzerland" expertise and U.S. filings.
  • 2026 Changes: Watch for FEIE inflation adjustments and tax return switzerland digital asset reporting (Form 1099-DA).

State-side moves? File part-year returns. Questions? Free IRS expat helpline: +1-267-941-1000.

Conclusion

 

Mastering tax advice for expats in 2026 means proactive filing, treaty savvy, and expert guidance to slash liabilities legally. Whether optimizing your tax return in Switzerland or elsewhere, these strategies empower financial freedom abroad. Don't go it alone—contact 1291 Group today for a free expat tax audit and personalized plan. Stay compliant, save big, and focus on living your best life overseas.

Discussão (0)1
Entre ou crie uma conta para continuar
Artigo
· 4 hr atrás 5min de leitura

JSON2Class, the JSON to ObjectScript converter you've always wanted

How many times have you had to receive or generate a JSON and wished you could work on it using DTLs without having to deal with DynamicObjects trying to remember the name of each field? Do you want to break down and make your giant JSON file more digestible?

In my case, never, but I thought that someone might find it useful to have a feature that captures your JSON and breaks it down into a series of ObjectScript classes that you can work with more easily and conveniently.

Well then...behold JSON2Class in all its glory!

How does JSON2Class work?

It's very simple: it leverages Embedded Python's capabilities to slice and parse your JSON and generate the associated classes. These generated classes will be of two types:

  • %Persistent: for the main or root class.
  • %SerialObject: for all subclasses that will be attached to the main one.

To do this, it takes into consideration the following points:

Reserved words

Not just any property name that comes in your JSON is acceptable, so it will be modified by adding to the end of the JSON name, so that " language" will become " languageJSON".

Special characters

Special characters such as "_" are also  removed, so "patient_name" will now be called "patientname".

%JSONFIELDNAME

To prevent the class from changing its name when it is converted back to JSON, the %JSONFIELDNAME attribute has been added to the properties whose names are modified, allowing us to maintain the original label when exporting it to JSON.

Generating the classes

All the functionality is contained within the Utils.JSON2Class  class , and to invoke the generation process we have the following method:

ClassMethod Convert(
    json As %String,
    basePackage As %String = "App.Model",
    rootClassName As %String = "Root",
    outDir As %String = "/shared/generated"
) As %String

Let's analyze the attributes of the ClassMethod:

  • json: This will be our template JSON that we want to generate.
  • basePackage: The package in which all the classes will be implemented.
  • rootClassName: The name of the persistent class that will act as the root.
  • outDir: The local directory where the class files will be generated.

Example:

We started with a typical JSON, such as a FHIR resource of type patient:

{
	"resourceType": "Patient",
	"id": "example",
	"identifier": [
		{
			"use": "usual",
			"type": {
				"coding": [
					{
						"system": "http://terminology.hl7.org/CodeSystem/v2-0203",
						"code": "MR"
					}
				]
			},
			"system": "urn:oid:1.2.36.146.595.217.0.1",
			"value": "12345",
			"period": {
				"start": "2001-05-06"
			},
			"assigner": {
				"display": "Acme Healthcare"
			}
		}
	],
	"active": true,
	"name": [
		{
			"use": "official",
			"family": "Chalmers",
			"given": [
				"Peter",
				"James"
			]
		},
		{
			"use": "usual",
			"given": [
				"Jim"
			]
		},
		{
			"use": "maiden",
			"family": "Windsor",
			"given": [
				"Peter",
				"James"
			],
			"period": {
				"end": "2002"
			}
		}
	],
	"telecom": [
		{
			"use": "home"
		},
		{
			"system": "phone",
			"value": "(03) 5555 6473",
			"use": "work",
			"rank": 1
		},
		{
			"system": "phone",
			"value": "(03) 3410 5613",
			"use": "mobile",
			"rank": 2
		},
		{
			"system": "phone",
			"value": "(03) 5555 8834",
			"use": "old",
			"period": {
				"end": "2014"
			}
		}
	],
	"gender": "male",
	"birthDate": "1974-12-25",
	"_birthDate": {
		"extension": [
			{
				"url": "http://hl7.org/fhir/StructureDefinition/patient-birthTime",
				"valueDateTime": "1974-12-25T14:35:45-05:00"
			}
		]
	},
	"deceasedBoolean": false,
	"address": [
		{
			"use": "home",
			"type": "both",
			"text": "534 Erewhon St\nPeasantVille, Rainbow, Vic3999",
			"line": [
				"534 Erewhon St"
			],
			"city": "PleasantVille",
			"district": "Rainbow",
			"state": "Vic",
			"postalCode": "3999",
			"period": {
				"start": "1974-12-25"
			}
		}
	],
	"contact": [
		{
			"relationship": [
				{
					"coding": [
						{
							"system": "http://terminology.hl7.org/CodeSystem/v2-0131",
							"code": "N"
						}
					]
				}
			],
			"name": {
				"family": "du Marché",
				"_family": {
					"extension": [
						{
							"url": "http://hl7.org/fhir/StructureDefinition/humanname-own-prefix",
							"valueString": "VV"
						}
					]
				},
				"given": [
					"Bénédicte"
				]
			},
			"additionalName": [
				{
					"use": "nickname",
					"given": [
						"Béné"
					]
				}
			],
			"telecom": [
				{
					"system": "phone",
					"value": "+33 (237) 998327"
				}
			],
			"address": {
				"use": "home",
				"type": "both",
				"line": [
					"534 Erewhon St"
				],
				"city": "PleasantVille",
				"district": "Rainbow",
				"state": "Vic",
				"postalCode": "3999",
				"period": {
					"start": "1974-12-25"
				}
			},
			"additionalAddress": [
				{
					"use": "work",
					"line": [
						"123 Smart St"
					],
					"city": "PleasantVille",
					"state": "Vic",
					"postalCode": "3999"
				}
			],
			"gender": "female",
			"period": {
				"start": "2012"
			}
		}
	],
	"managingOrganization": {
		"reference": "Organization/1"
	}
}

Let's now look at the Root object, which will be our main patient class:

Let's now look at the Root object, which will be our main patient class:

Class App.Model.Root Extends (%Persistent, %JSON.Adaptor)
{

Property resourceType As %String;
Property idJSON As %String(%JSONFIELDNAME = "id");
Property identifier As list Of App.Model.Root.Identifier;
Property active As %Boolean;
Property name As list Of App.Model.Root.Name;
Property telecom As list Of App.Model.Root.Telecom;
Property gender As %String;
Property birthDate As %String;
Property deceasedBoolean As %Boolean;
Property address As list Of App.Model.Root.Address;
Property contact As list Of App.Model.Root.Contact;
Property managingOrganization As App.Model.Root.ManagingOrganization;
}

Et voila! We can now store our JSON as a regular object.

Next steps

It's not bad to be able to automatically generate the classes, but it would be interesting to be able to automatically transform the JSON into an instance of the classes we have created, taking into account the particularities of the property names.

We'll leave it in the to-do pile

homer simpson sits on a couch next to a stack of papers and a can of duff beer

Discussão (0)1
Entre ou crie uma conta para continuar
Artigo
· 4 hr atrás 5min de leitura

JSON2Class, el conversor de JSON a ObjectScript que siempre deseaste

¿Cuantas veces habéis tenido que recibir o generar un JSON y habéis añorado el poder trabajar sobre él haciendo uso de DTLs y sin tener que ir manejando DynamicObjects intentando recordar cual era el nombre de cada campo?

¿Deseas trocear y hacer más digerible tu gigantesco JSON?

En mi caso, nunca, pero he pensado que a alguien le podría resultar de utilidad una funcionalidad que capture tu JSON y lo descomponga en una serie de clases de ObjectScript con las que puedas trabajar de forma más cómoda y sencilla.

Pues bien...¡contemplad el JSON2Class en toda su gloria!

¿Cómo funciona JSON2Class?

Muy sencillo, aprovecha las capacidades de Embedded Python para trocear y analizar tu JSON y generar las clases asociadas al mismo. Estas clases generadas serán de dos tipos:

  • %Persistent: para la clase principal o root.
  • %SerialObject: para todas las subclases que colgarán de la principal.

Para ello tiene en consideración los siguientes puntos:

Palabras reservadas

No nos vale cualquier nombre de propiedad que venga en tu JSON, por lo que se modificará añadiendo al final del nombre JSON, de tal forma que "language" pasará a ser "languageJSON".

Carácteres especiales

También se eliminan los carácteres especiales como "_", por lo que "patient_name" pasará a denominarse "patientname".

%JSONFIELDNAME

Para evitar que a la hora de convertir nuevamente la clase a JSON se han añadido a las propiedades que ven modificados sus nombres el atributo %JSONFIELDNAME que nos permite mantener la etiqueta original cuando lo exportemos a JSON.

Generando las clases

Toda la funcionalidad se encuentra dentro de la clase Utils.JSON2Class y para invocar el proceso de generación disponemos del método:

ClassMethod Convert(
    json As %String,
    basePackage As %String = "App.Model",
    rootClassName As %String = "Root",
    outDir As %String = "/shared/generated"
) As %String

Analicemos los atributos del ClassMethod:

  • json: será nuestro json de plantilla que queremos generar. 
  • basePackage: el package sobre el que se implementarán todas las clases. 
  • rootClassName: el nombre de la clase persistente que ejercerá de raíz.
  • outDir: directorio local donde se van a generar los ficheros de las clases.

Ejemplo:

Hemos partido de un JSON típico como sería un recurso FHIR de tipo paciente:

{
	"resourceType": "Patient",
	"id": "example",
	"identifier": [
		{
			"use": "usual",
			"type": {
				"coding": [
					{
						"system": "http://terminology.hl7.org/CodeSystem/v2-0203",
						"code": "MR"
					}
				]
			},
			"system": "urn:oid:1.2.36.146.595.217.0.1",
			"value": "12345",
			"period": {
				"start": "2001-05-06"
			},
			"assigner": {
				"display": "Acme Healthcare"
			}
		}
	],
	"active": true,
	"name": [
		{
			"use": "official",
			"family": "Chalmers",
			"given": [
				"Peter",
				"James"
			]
		},
		{
			"use": "usual",
			"given": [
				"Jim"
			]
		},
		{
			"use": "maiden",
			"family": "Windsor",
			"given": [
				"Peter",
				"James"
			],
			"period": {
				"end": "2002"
			}
		}
	],
	"telecom": [
		{
			"use": "home"
		},
		{
			"system": "phone",
			"value": "(03) 5555 6473",
			"use": "work",
			"rank": 1
		},
		{
			"system": "phone",
			"value": "(03) 3410 5613",
			"use": "mobile",
			"rank": 2
		},
		{
			"system": "phone",
			"value": "(03) 5555 8834",
			"use": "old",
			"period": {
				"end": "2014"
			}
		}
	],
	"gender": "male",
	"birthDate": "1974-12-25",
	"_birthDate": {
		"extension": [
			{
				"url": "http://hl7.org/fhir/StructureDefinition/patient-birthTime",
				"valueDateTime": "1974-12-25T14:35:45-05:00"
			}
		]
	},
	"deceasedBoolean": false,
	"address": [
		{
			"use": "home",
			"type": "both",
			"text": "534 Erewhon St\nPeasantVille, Rainbow, Vic3999",
			"line": [
				"534 Erewhon St"
			],
			"city": "PleasantVille",
			"district": "Rainbow",
			"state": "Vic",
			"postalCode": "3999",
			"period": {
				"start": "1974-12-25"
			}
		}
	],
	"contact": [
		{
			"relationship": [
				{
					"coding": [
						{
							"system": "http://terminology.hl7.org/CodeSystem/v2-0131",
							"code": "N"
						}
					]
				}
			],
			"name": {
				"family": "du Marché",
				"_family": {
					"extension": [
						{
							"url": "http://hl7.org/fhir/StructureDefinition/humanname-own-prefix",
							"valueString": "VV"
						}
					]
				},
				"given": [
					"Bénédicte"
				]
			},
			"additionalName": [
				{
					"use": "nickname",
					"given": [
						"Béné"
					]
				}
			],
			"telecom": [
				{
					"system": "phone",
					"value": "+33 (237) 998327"
				}
			],
			"address": {
				"use": "home",
				"type": "both",
				"line": [
					"534 Erewhon St"
				],
				"city": "PleasantVille",
				"district": "Rainbow",
				"state": "Vic",
				"postalCode": "3999",
				"period": {
					"start": "1974-12-25"
				}
			},
			"additionalAddress": [
				{
					"use": "work",
					"line": [
						"123 Smart St"
					],
					"city": "PleasantVille",
					"state": "Vic",
					"postalCode": "3999"
				}
			],
			"gender": "female",
			"period": {
				"start": "2012"
			}
		}
	],
	"managingOrganization": {
		"reference": "Organization/1"
	}
}

Y al ejecutar el conversor hemos obtenido las siguientes clases:

Veamos ahora el objeto Root, que será nuestra clase principal del paciente:

Class App.Model.Root Extends (%Persistent, %JSON.Adaptor)
{

Property resourceType As %String;

Property idJSON As %String(%JSONFIELDNAME = "id");

Property identifier As list Of App.Model.Root.Identifier;

Property active As %Boolean;

Property name As list Of App.Model.Root.Name;

Property telecom As list Of App.Model.Root.Telecom;

Property gender As %String;

Property birthDate As %String;

Property deceasedBoolean As %Boolean;

Property address As list Of App.Model.Root.Address;

Property contact As list Of App.Model.Root.Contact;

Property managingOrganization As App.Model.Root.ManagingOrganization;

}

Et voila! Ya podemos almacenar nuestro JSON como un objeto al uso.

Siguientes pasos

No esta mal poder generar automáticamente las clases, pero será interesante poder transformar automáticamente el JSON a una instancia de las clases que hemos creado teniendo en cuenta las particularidades de los nombres de las propiedades.

Lo dejaremos en la pila de cosas por hacer.

homer simpson sits on a couch next to a stack of papers and a can of duff beer

Discussão (0)1
Entre ou crie uma conta para continuar